Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107212)
Summary
Vulnerability in github.com/xuri/excelize/v2 (CVE-2026-107212). Risk of unauthorized operations or information disclosure. Exploitable via File.GetRows. Mitigation: upgrade to 2.11.1-0.20260930021559-01a9ff32fb3c or later.
Original description
The description as published by the source.
Summary
A worksheet whose number is far past Excel's 1,048,576-row limit makes `File.GetRows` and the `Rows` iterator loop once for every missing row. The row limit is checked in `Rows.Next`, but not in `Rows.Columns`, which also reads elements. A 1.5 KB file with `` after an ordinary first row keeps GetRows busy for an estimated 11 days (about 4 ns per missing row), using one CPU core and little memory. Any service that calls GetRows or iterates Rows on an uploaded workbook can be tied up by a single request.
Details
Rows.Next checks the row number:
rowNum, _ := attrValToInt("r", xmlElement.Attr)
if rowNum > TotalRows {
rows.err = ErrMaxRows
return false
}
But Rows.Columns reads the cells of the current row by consuming tokens until it reaches the next `` element, and it sets rows.curRow from that element's r without the check (rows.go, around line 179 at 3985c1f):
if rowNum, rowIterator.err = attrValToInt("r", xmlElement.Attr); rowNum != 0 {
rows.curRow = rowNum
}
After that, rows.curRow is 231999999999940, and each later Next() call takes the rows.curRow >= rows.seekRow shortcut and returns true without reading any XML. GetRows then calls Next() and Columns() once per row number from 2 to 231999999999940. The check in Next() never runs, because the oversized `` element was already consumed by Columns().
If the oversized row is the first row, Next() reads it and the existing check wo…
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-107212 has been found in github.com/xuri/excelize/v2.
Attackers can target a specific entry point like File.GetRows over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/xuri/excelize/v2 to 2.11.1-0.20260930021559-01a9ff32fb3c or later.
If unsure, ask your IT team or search "github.com/xuri/excelize/v2 CVE-2026-107212" on the vendor's site.
CVE-2026-107212 (github.com/xuri/excelize/v2) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: File.GetRows / Rows / Rows.Next / Rows.Columns
Patched: 2.11.1-0.20260930021559-01a9ff32fb3c — 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-770) exists in github.com/xuri/excelize/v2. Attackers reach the vulnerable code path via File.GetRows without authentication.
Check the vendor advisory for the affected versions of github.com/xuri/excelize/v2. Attack surface: File.GetRows / Rows / Rows.Next / Rows.Columns.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.11.1-0.20260930021559-01a9ff32fb3c.
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.20260930021559-01a9ff32fb3cステージング環境で 2.11.1-0.20260930021559-01a9ff32fb3c に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- exploit security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web nvd.nist.gov
- web github.com