qax-os excelize up to 2.11.0 Style Extraction styles.xml GetStyle fillId/borderId/fontId input validation

Summaryinfo

A vulnerability classified as problematic has been found in qax-os excelize up to 2.11.0. Affected by this issue is the function GetStyle of the file styles.xml of the component Style Extraction. This manipulation of the argument fillId/borderId/fontId causes input validation. This vulnerability is handled as CVE-2026-107225. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in qax-os excelize up to 2.11.0. It has been declared as problematic. Affected by this vulnerability is the function GetStyle of the file styles.xml of the component Style Extraction. The manipulation of the argument fillId/borderId/fontId with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect availability. The summary by CVE is:

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.8.0 to 2.11.0, GetStyle's fill, border, and font extraction predicates check only upper bounds for attacker-controlled style-table indices. File.GetStyle relies on extractStyleCondFuncs predicates that allow negative FillID, BorderID, and FontID values to reach slice indexing. When a crafted styles.xml supplies a negative fillId, borderId, or fontId and the application reads the style, a negative identifier passes the upper-bound-only predicate and becomes a negative slice index, allowing an attacker to panic while reading cell styling. No fixed version is available as of this review.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-107225 since 10/07/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/07/2026).

By approaching the search of inurl:styles.xml it is possible to find vulnerable targets with Google Hacking.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion