What’s Vulnerable › Vulnerabilities
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
- Severity: high (CVSS 7.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2026-10-07 · updated 2026-10-13
- Weakness: CWE-129
Description
Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. From 2.0.0 to 2.11.0 in github.com/xuri/excelize/v2 and from 1.1.0 to 1.4.1 in github.com/xuri/excelize, ColumnNameToNumber accumulates a bijective base-26 value in int64 without detecting overflow, allowing an invalid long column name to wrap to zero with no error. ColumnNameToNumber accepts the overflowing name VGWQHXLSDVIKWV, after which checkSheetR0 and xlsxWorksheet.checkRow use the wrapped column value as an index. When a crafted worksheet uses an overflowing column name in a row normalized by checkSheetR0 or checkRow, the wrapped zero column becomes a negative slice index during worksheet normalization, allowing an attacker to panic and terminate the calling process. No fixed version is available as of this review.
Affected products
- qax-os excelize: from 1.1.0 through 1.4.1; from 2.0.0 through 2.11.0
References
- https://github.com/qax-os/excelize/commit/696050fbf14e74e96a58eef2b16aaf72f381a6a8
- https://github.com/qax-os/excelize/pull/2394
- https://github.com/qax-os/excelize/security/advisories/GHSA-c85p-xxjj-2r75
- https://github.com/qax-os/excelize/security/advisories/GHSA-c85p-xxjj-2r75
Get alerted when CVE-2026-107217 or the next vulnerability affects your stack