Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation

Exploitation

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

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

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

Streaming GetRows row-bound bypass causes attacker-controlled allocation Summary Excelize's prior row-bound fix for GHSA-h69g / CVE-2026-54063 protects the checked worksheet parser, but the streaming worksheet reader used by Rows and GetRows does not enforce the same TotalRows bound on the row r attribute. A small XLSX file can set a row number above Excelize's maximum row (1048576) and omit the cell coordinate. GetRows then appends empty rows up to the attacker-controlled row index and returns success. This was reproduced on the current default branch commit 1213a8bd7c5ab360554603ac5c995ccaf6eb4314 and the latest release tag v2.10.1 (5ad5ab3af0054c55bdce09f1530085600e9f2e45). Affected package - Package: github.com/xuri/excelize/v2 - Tested affected versions: current default branch at 1213a8bd7c5ab360554603ac5c995ccaf6eb4314, and release v2.10.1 - Fixed version: none known at the time of this report Impact An attacker who can provide an XLSX file to an application that calls GetRows…

Published by the source

10 Sep 2026, 15:09 UTC

Last modified by the source

17 Sep 2026, 17:30 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q5j5-6p94-4gwc

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6453

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q5j5-6p94-4gwc

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

# Patch Next advisory brief: CVE-2026-59161

Advisory: Excelize: Streaming GetRows row-bound bypass causes attacker-controlled allocation
IDs: CVE-2026-59161, GHSA-q5j5-6p94-4gwc
Record: https://patchnext.com/advisories/cve-2026-59161 (revision 4, 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 8.7)
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.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/xuri/excelize: affected <= 1.4.0
- Go github.com/xuri/excelize/v2: affected < 2.11.0; fixed in 2.11.0

## 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-q5j5-6p94-4gwc (OSV record GHSA-q5j5-6p94-4gwc lists affected ranges: Go github.com/xuri/excelize/v2 >=0 =0 <=1.4.0)
- Verified: https://osv.dev/vulnerability/GO-2026-6453 (OSV record GO-2026-6453 lists affected ranges: Go github.com/xuri/excelize/v2 >=0 <2.11.0 (fixed))
- Verified: https://github.com/advisories/GHSA-q5j5-6p94-4gwc (GitHub-reviewed advisory GHSA-q5j5-6p94-4gwc lists affected ranges: Go github.com/xuri/excelize/v2 >=0 =0 <=1.4.0)

Commands are suggestions: review each one before running it.