Excelize ColumnNameToNumber: int64 overflow yields an out-of-domain coordinate with nil error, causing negative slice index panic on r="0" rows

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-107217: 0.36% estimated exploitation activity in the next 30 days; percentile 30.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary ColumnNameToNumber (lib.go:220-237) accumulates the bijective base-26 value of a column name in an int64 with only an upper-bound check (col MaxColumns) applied after the loop and no overflow detection. A 14-letter column name whose true value is 3·2⁶⁴ — e.g. VGWQHXLSDVIKWV — wraps to col = 0 and passes the guard, so CellNameToCoordinates("VGWQHXLSDVIKWV1") returns (col=0, row=1, err=nil). When normalizing a r="0" row, checkSheetR0 (excelize.go:417-443, called from checkSheet at excelize.go:405) runs its checkRow closure with col = 0: colIdx := col - 1 becomes -1, and sheetData.Row[rowIdx].C[-1] (excelize.go:424) raises an unrecovered panic: runtime error: index out of range [-1], killing the host process. Details - The row side of the same coordinate gate is enforced (checkRowNum at excelize.go:342-350 bounds r before the make([]xlsxRow, row) allocation; this includes the fix for GHSA-h69g-9hx6-f3v4 / CVE-2026-54063, present in the audited commit). The column side is not:…

Published by the source

7 Oct 2026, 20:23 UTC

Last modified by the source

7 Oct 2026, 20:30 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-c85p-xxjj-2r75

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-c85p-xxjj-2r75

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107217

Advisory: Excelize ColumnNameToNumber: int64 overflow yields an out-of-domain coordinate with nil error, causing negative slice index panic on r="0" rows
IDs: CVE-2026-107217, GHSA-c85p-xxjj-2r75
Record: https://patchnext.com/advisories/cve-2026-107217 (revision 2, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/xuri/excelize/v2 2.11.1-0.20260910071107-696050fbf14e. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize: affected >= 1.1.0, <= 1.4.1
- Go github.com/xuri/excelize/v2: affected >= 2.0.0, < 2.11.1-0.20260910071107-696050fbf14e; fixed in 2.11.1-0.20260910071107-696050fbf14e

## Suggested inspection (read-only)
- Go github.com/xuri/excelize: check the installed version with your package manager.
- Go github.com/xuri/excelize/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/xuri/excelize, github.com/xuri/excelize/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-c85p-xxjj-2r75 (OSV record GHSA-c85p-xxjj-2r75 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.0.0 =1.1.0 <=1.4.1)
- Verified: https://github.com/advisories/GHSA-c85p-xxjj-2r75 (GitHub-reviewed advisory GHSA-c85p-xxjj-2r75 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.0.0 =1.1.0 <=1.4.1)

Commands are suggestions: review each one before running it.