Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days

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-107212: 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 A worksheet whose <row r="..." 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 <row elements. A 1.5 KB file with <row r="231999999999940" 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: But Rows.Columns reads the cells of the current row by consuming tokens until it reaches the next <row element, and it sets rows.curRow from that element's r without the check (rows.go, around line 179 at 3985c1f): 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…

Published by the source

8 Oct 2026, 16:50 UTC

Last modified by the source

19 Oct 2026, 21:31 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-jw42-f3rr-4cc3

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6685

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-jw42-f3rr-4cc3

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

# Patch Next advisory brief: CVE-2026-107212

Advisory: Excelize: Unbounded row number in Rows.Columns makes GetRows and the Rows iterator loop for days
IDs: CVE-2026-107212, GHSA-jw42-f3rr-4cc3
Record: https://patchnext.com/advisories/cve-2026-107212 (revision 3, 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.20260930021559-01a9ff32fb3c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/360EntSecGroup-Skylar/excelize/v2: affected >= 2.1.0
- Go github.com/xuri/excelize/v2: affected >= 2.1.0, < 2.11.1-0.20260930021559-01a9ff32fb3c; fixed in 2.11.1-0.20260930021559-01a9ff32fb3c

## Suggested inspection (read-only)
- Go github.com/360EntSecGroup-Skylar/excelize/v2: 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/360EntSecGroup-Skylar/excelize/v2, 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/GO-2026-6685 (OSV record GO-2026-6685 lists affected ranges: Go github.com/360EntSecGroup-Skylar/excelize/v2 >=2.1.0; Go github.com/xuri/excelize/v2 >=0 <2.11.1-0.20260930021559-01a9ff32fb3c (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-jw42-f3rr-4cc3 (OSV record GHSA-jw42-f3rr-4cc3 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.1.0 <2.11.1-0.20260930021559-01a9ff32fb3c (fixed))
- Verified: https://github.com/advisories/GHSA-jw42-f3rr-4cc3 (GitHub-reviewed advisory GHSA-jw42-f3rr-4cc3 lists affected ranges: Go github.com/xuri/excelize/v2 >=2.1.0 <2.11.1-0.20260930021559-01a9ff32fb3c)

Commands are suggestions: review each one before running it.