qax-os excelize up to 2.11.0 Pivot Table Processing extractPivotTableFields fld memory corruption

Summaryinfo

A vulnerability was found in qax-os excelize up to 2.11.0. It has been declared as problematic. This affects the function extractPivotTableFields of the component Pivot Table Processing. Executing a manipulation of the argument fld can lead to memory corruption. This vulnerability is registered as CVE-2026-107211. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability has been found in qax-os excelize up to 2.11.0 and classified as problematic. This vulnerability affects the function extractPivotTableFields of the component Pivot Table Processing. The manipulation of the argument fld with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect availability. CVE summarizes:

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.8.1 to 2.11.0, separately parsed pivot-table field indices are used to index the pivot-cache field-name slice without bounds checks. extractPivotTableFields uses getPivotCacheFieldsName output while processing GetPivotTables and trusts the dataField fld attribute as an index. When a crafted workbook supplies a pivot-field count mismatch or an out-of-range dataField fld value before GetPivotTables is called, the unchecked index causes a Go slice-bounds panic that escapes the library, allowing an attacker to crash the process or request worker. No fixed version is available as of this review.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-107211 since 10/07/2026. The exploitation appears to be easy. The attack can be initiated remotely. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/07/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• qax-os

Name

• excelize

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11.0

Website

• Product: https://github.com/qax-os/excelize/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion