CVE-2026-107225 · GHSA-5h23-36rv-pm65
Excelize: GetStyle panics on a negative fillId, borderId or fontId in styles.xml
- Risk score
- 52/100
- CVSS
- 6.5 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 7 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it 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,…
- Affected
- github.com/xuri/excelize/v2 (go) >= 2.8.0, < 2.11.1-0.20260731010303-ae2113b410e5
- Fix
- Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260731010303-ae2113b410e5 or later.
- Exploitation
- Public proof of concept
Story map
At a glance
github.com/xuri/excelize/v2: Amber, patch this week. Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.1.0 to 2.11.0, flatCols expands file-loaded column ranges without validating Min and Max against the worksheet column limit. SetColWidth reaches flatCols, which expands xlsxCol.Min through xlsxCol.Max without enforcing MaxCo…
The flaws
- CVE-2026-107225: Excelize: GetStyle panics on a negative fillId, borderId or fontId in styles.xml (CVSS 6.5 · EPSS 0%)
- CVE-2026-107223: Excelize: Unbounded <col max> attribute is loaded with no MaxColumns check and expanded per-column by flatCols(), so any column mutator hangs or OOMs the process (CVSS 7.5 · EPSS 0%)
- CVE-2026-107212: Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days (CVSS 7.5 · EPSS 0%)
- CVE-2026-107217: Excelize ColumnNameToNumber: int64 overflow yields an out-of-domain coordinate with nil error, causing negative slice index panic on r="0" rows (CVSS 7.5 · EPSS 0%)
The fix
Fix: Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260807015645-a54c578af309 or later.
Who is exposed: github.com/xuri/excelize/v2 (go) >= 2.1.0, < 2.11.1-0.20260807015645-a54c578af309
Where it stands
- Public proof of concept
Connects to
- Same weakness: CWE-129 (CWE-129). 22 other warnings in 30 days
- Same product: Earlier github.com/xuri/excelize/v2 warnings. 11 in the last 90 days
Why it is Yellow
- CVSS 6.5 medium
- Public exploit or proof of concept referenced
- On your watchlist: Go
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| github.com/xuri/excelize/v2 | go | >= 2.8.0, < 2.11.1-0.20260731010303-ae2113b410e5 | 2.11.1-0.20260731010303-ae2113b410e5 |
References
Original 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.
Last activity 7 Oct 2026. Patch Forecast updates every hour.