Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107222)
Summary
Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107222). Risk of unauthorized operations or information disclosure. Exploitable via GetConditionalFormats. Mitigation: upgrade to 2.11.1-0.20260812075026-be7a16390fa6 or later.
Original description
The description as published by the source.
Summary
GetConditionalFormats reads sub-elements of a `` straight out of xl/worksheets/sheetN.xml and indexes them without checking length, and in one case without checking for nil. Three rule types are affected: cellIs, dataBar and colorScale. A workbook with a rule that is missing a child a real Excel file would always have panics the call.
Where it is
All three sinks are in styles.go, at the same line numbers in v2.11.0 and on master d552a7e. All three are reached from GetConditionalFormats through styles.go:3271.
styles.go:3003, in extractCondFmtCellIs:
format.Value = c.Formula[0]
The branch above it handles len(c.Formula) == 2; this one is the fallback and does not check that there is a formula at all, so a cellIs rule with no `` child indexes an empty slice.
styles.go:3132, in the colorScale extractor:
values := len(c.ColorScale.Cfvo)
c.ColorScale is a *xlsxColorScale and is nil when the element has no child. Lines 3148 and 3153 then index Cfvo[1] and Cfvo[2] in the three-colour branch with no length check either.
styles.go:3186, :3188 and :3190, in the dataBar extractor:
format.MinType = c.DataBar.Cfvo[0].Type
...
format.BarColor = "#" + f.getThemeColor(c.DataBar.Color[0])
The guard here is c.DataBar != nil, which says nothing about the length of Cfvo or Color, so an empty `` element reaches all three.
Who the attacker is
Anyone who can hand a spreadsheet…
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-107222 has been found in github.com/xuri/excelize/v2.
Attackers can target a specific entry point like GetConditionalFormats 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.20260812075026-be7a16390fa6 or later.
If unsure, ask your IT team or search "github.com/xuri/excelize/v2 CVE-2026-107222" on the vendor's site.
CVE-2026-107222 (github.com/xuri/excelize/v2) — CWE-129 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GetConditionalFormats / cellIs / dataBar / colorScale
Patched: 2.11.1-0.20260812075026-be7a16390fa6 — 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-129) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via GetConditionalFormats without authentication.
Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: GetConditionalFormats / cellIs / dataBar / colorScale.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.11.1-0.20260812075026-be7a16390fa6.
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.20260812075026-be7a16390fa6ステージング環境で 2.11.1-0.20260812075026-be7a16390fa6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com