CVE-2026-107225 json
Excelize: GetStyle panics on a negative fillId, borderId or fontId in styles.xml
published last mo. modified 4d ago also EUVD-2026-94556 , GHSA-5h23-36rv-pm65 , GO-2026-6674
- 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
- github.com/qax-os/excelize@ae2113b commit
- github.com/qax-os/excelize#2367 pull request
Is CVE-2026-107225 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 30d ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
References
-
github.com
/qax-os/excelize/pull/2367
web, issue-tracking, patch
-
github.com
/qax-os/excelize/commit/ae2113b410e51f6a141c396a59eda8c42b91bc22
web, patch
-
github.com
/qax-os/excelize/security/advisories/GHSA-5h23-36rv-pm65
exploit, web, vendor-advisory, advisory
-
github.com
/qax-os/excelize
package
Sources
- CVE List CVE-2026-107225
- GitHub Advisory GHSA-5h23-36rv-pm65
- NVD CVE-2026-107225
- OSV GO-2026-6674
Fencer Intel 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.