Skip to content
Fencer Vulns
medium 6.5

CVE-2026-107225 json

Excelize: GetStyle panics on a negative fillId, borderId or fontId in styles.xml

published 2026-10-07 32 d ago modified 2026-11-05 3 d ago also GHSA-5h23-36rv-pm65 , GO-2026-6674 , EUVD-2026-94556

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 19%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/xuri/excelize/v2 2.11.1-0.20260731010303-ae2113b410e5

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
30 d ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/qax-os/excelize/security/advisories/GHSA-5h23-36rv-pm65 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/xuri/excelize/v2
>=2.8.0, <2.11.1-0.20260731010303-ae2113b410e5
2.11.1-0.20260731010303-ae2113b410e5

Affected products

  • qax-os excelize

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-129 Improper Validation of Array Index

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.