Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107225)
Summary
Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107225). Risk of unauthorized operations or information disclosure. Exploitable via File.GetStyle. Mitigation: upgrade to 2.11.1-0.20260731010303-ae2113b410e5 or later.
Original description
The description as published by the source.
Summary
File.GetStyle indexes the fill, border and font tables with values taken straight out of xl/styles.xml, and the conditions gating those lookups check only the upper bound. A workbook whose cellXfs entry carries fillId="-1", borderId="-1" or fontId="-1" reaches a negative slice index and panics. excelize has no recover(), so the panic leaves GetStyle and takes the calling process with it.
Same defect class as GHSA-48hm-4h8j-58fg, the negative shared-string index, in a different file. That one was fixed by adding the missing lower bound; these three sites still lack it.
Where it is
styles.go, in GetStyle, lines 1683, 1686 and 1689:
xf := s.CellXfs.Xf[idx]
if extractStyleCondFuncs["fill"](xf, s) {
f.extractFills(s.Fills.Fill[*xf.FillID], s, style)
}
if extractStyleCondFuncs["border"](xf, s) {
f.extractBorders(s.Borders.Border[*xf.BorderID], s, style)
}
if extractStyleCondFuncs["font"](xf, s) {
style.Font = extractFont(s.Fonts.Font[*xf.FontID])
}
The conditions, at lines 1171 to 1185, bound only the top:
"fill": func(xf xlsxXf, s *xlsxStyleSheet) bool {
return (xf.ApplyFill == nil || (xf.ApplyFill != nil && *xf.ApplyFill)) &&
xf.FillID != nil && s.Fills != nil &&
*xf.FillID < len(s.Fills.Fill)
},
*xf.FillID < len(...) is satisfied by any negative value. FillID, BorderID and FontID are *int unmarshalled directly from the fillId, borderId and fontId attributes, so the value…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107225 has been found in github.com/xuri/excelize/v2.
Attackers can target a specific entry point like File.GetStyle over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260731010303-ae2113b410e5 or later.
If unsure, ask your IT team or search "github.com/xuri/excelize/v2 CVE-2026-107225" on the vendor's site.
CVE-2026-107225 (github.com/xuri/excelize/v2) — CWE-20 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: File.GetStyle / cellXfs / GetStyle / styles.go
Patched: 2.11.1-0.20260731010303-ae2113b410e5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via File.GetStyle without authentication.
Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: File.GetStyle / cellXfs / GetStyle / styles.go.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.11.1-0.20260731010303-ae2113b410e5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/xuri/excelize/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/xuri/excelize/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/xuri/excelize/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260731010303-ae2113b410e5ステージング環境で 2.11.1-0.20260731010303-ae2113b410e5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- exploit github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com