Excelize: a row whose earlier cell has a higher column reference than its last cell panics index out of range on almost every worksheet read API

Exploitation

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

CVSS

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

EPSS

• CVE-2026-107221: 0.27% estimated exploitation activity in the next 30 days; percentile 19.24 (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.

Affected versions and vulnerable location - Confirmed at ae2113b (current HEAD). - Sink: rows.go:967 ws.SheetData.Row[rowIdx].C[colNum-1] = colData inside checkRow. - checkRow computes lastCol from the column of the last cell in document order (rows.go:940), allocates targetList of that length, then re-scatters every source cell into C[colNum-1]. Root cause The slice is sized from the last cell's column, but cells are not required to be column-sorted in the XML. A cell that appears earlier in the row but references a higher column than the last cell has colNum-1 = len(targetList), so the assignment writes out of range. MaxColumns/TotalRows do not help, every individual column is valid; the bug is the ordering assumption, not magnitude. Attacker model and reachability Any service that opens an untrusted spreadsheet and calls a worksheet API that goes through workSheetReader - checkRow (excelize.go:332): GetCellValue, GetCellFormula, CalcCellValue, GetMergeCells, SetCellValue, and…

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-8mcq-6wmr-jrjv

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8mcq-6wmr-jrjv

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

# Patch Next advisory brief: CVE-2026-107221

Advisory: Excelize: a row whose earlier cell has a higher column reference than its last cell panics index out of range on almost every worksheet read API
IDs: CVE-2026-107221, GHSA-8mcq-6wmr-jrjv
Record: https://patchnext.com/advisories/cve-2026-107221 (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: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/xuri/excelize/v2 2.11.1-0.20260816084418-46a5eb289448. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize/v2: affected >= 2.0.0, < 2.11.1-0.20260816084418-46a5eb289448; fixed in 2.11.1-0.20260816084418-46a5eb289448

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on 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-8mcq-6wmr-jrjv (OSV record GHSA-8mcq-6wmr-jrjv lists affected ranges: Go github.com/xuri/excelize/v2 >=2.0.0 <2.11.1-0.20260816084418-46a5eb289448 (fixed))
- Verified: https://github.com/advisories/GHSA-8mcq-6wmr-jrjv (GitHub-reviewed advisory GHSA-8mcq-6wmr-jrjv lists affected ranges: Go github.com/xuri/excelize/v2 >=2.0.0 <2.11.1-0.20260816084418-46a5eb289448)

Commands are suggestions: review each one before running it.