Skip to main content
Public proof of conceptFix available

CVE-2026-107225

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

A public proof of concept exists; no exploitation attested.

  • Published2026-10-07
  • WeaknessCWE-129 · CWE-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-10-0719:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-107225?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-107225?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Excelize
BranchAffectedFixed in
2.x≥ 2.8.0, ≤ 2.11.0no fix published
xuri/excelize
BranchAffectedFixed in
2.x≥ 2.8.0, < 2.11.1-0.20260731010303-ae2113b410e52.11.1-0.20260731010303-ae2113b410e5

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-10-10
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.16.5read 2026-10-23
  • CNAweakness (CWE)CWE-129, CWE-20read 2026-10-23
  • FIRST EPSSEPSS score0.3 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2026-10-07
Last Modified
2026-10-13
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-107225?

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.

Is CVE-2026-107225 actively exploited?

A proof-of-concept exploit exists for CVE-2026-107225, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-107225?

CVE-2026-107225 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running xuri/excelize? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database