Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. Prior to 2.11.0, the streaming worksheet reader used by Rows and GetRows does not enforce the TotalRows limit on the row r attribute, allowing a small XLSX file with a row number above 1048576 and no cell coordinate to make GetRows append empty rows up to the attacker-controlled index and consume excessive memory and CPU. This issue is fixed in version 2.11.0.
CVE-2026-59161
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 59% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EPSS
- 40.7%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 10, 2026Streaming GetRows row-bound bypass causes attacker-controlled allocation · Advisory · qax-os/excelize · GitHub
https://github.com/qax-os/excelize/security/advisories/GHSA-q5j5-6p94-4gwcv2.11.0
Patch available: qax-os/excelize v2.11.0
https://github.com/qax-os/excelize/releases/tag/v2.11.0This fixes security advisories GHSA-q5j5-6p94-4gwc and GHSA-fx5j-qcqg-grpf
Patch available: qax-os/excelize v2.11.0 (PR #2331 merged 2026-06-21)
https://github.com/qax-os/excelize/pull/2331commit 93f0b3caed37 (qax-os/excelize)
Patch available: qax-os/excelize v2.11.0 (contains commit 93f0b3caed37)
https://github.com/qax-os/excelize/commit/93f0b3caed37f21ef5079e3259c6c21dcfe68453Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 04:50 UTCEG score recompute
- 2026-07-12 16:47 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 04:43 UTCEG score recompute
- 2026-07-11 16:40 UTCEG score recompute
- 2026-07-11 04:37 UTCEG score recompute
- 2026-07-10 16:33 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-59161?
When was CVE-2026-59161 disclosed?
Is CVE-2026-59161 actively exploited?
What is the CVSS score of CVE-2026-59161?
How do I remediate CVE-2026-59161?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59161
Is Your Infrastructure Affected by CVE-2026-59161?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.