Quick answers
- Is CVE-2026-59162 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59162 being exploited in the wild.
- How severe is CVE-2026-59162?
- Medium severity, with a CVSS score of 4, published 10 July 2026.
- Which products and versions are affected?
- github.com/xuri/excelize (Go) <= 1.4.0, SEMVER:introduced=0,last_affected=1.4.0; github.com/xuri/excelize/v2 (Go) < 2.11.0, SEMVER:introduced=0,fixed=2.11.0; Xuri Excelize < 2.11.0, <= 1.4.0.
- Is there a fix for CVE-2026-59162?
- Yes. github.com/xuri/excelize/v2 (Go): upgrade to 2.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59162 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59162?
- Check whether you run github.com/xuri/excelize (Go), github.com/xuri/excelize/v2 (Go) or Xuri Excelize at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/xuri/excelize/v2 (Go): upgrade to 2.11.0 or later
go get github.com/xuri/excelize/v2@v2.11.0
Technical details
The vulnerability is an uncaught exception in the xlsxC.getValueFrom() function. When processing XLSX cells with the shared-string type (t="s"), the code parses the cell value as an integer index and validates only that len(d.SI) > xlsxSI, omitting a lower-bound check for negative indices. A malicious XLSX workbook containing a cell with <v>-1</v> will cause a panic during GetCellValue() or GetRows() calls without explicit panic recovery. The attack requires the victim application to process an attacker-supplied XLSX file. The fix, released in v2.11.0, adds a bounds check: if xlsxSI >= 0 && xlsxSI < len(d.SI).
Affected products
- xuri excelize <= 1.4.0
- xuri excelize/v2 < 2.11.0
Identifiers
- CVE-2026-59162
- GHSA-fx5j-qcqg-grpf
- GO-2026-6452
Timeline
- 2026-09-10: disclosed: Vulnerability published to GitHub Advisory Database
- 2026-06-21: patched: Patch released in v2.11.0 (commit 93f0b3c)