Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. Prior to 2.11.0, the checkSheet() function in github.com/xuri/excelize/v2 uses an attacker-controlled XML attribute value directly as the length argument to make([]xlsxRow, row) without validating it against the Excel row limit (TotalRows = 1,048,576). A specially crafted XLSX file can trigger two denial-of-service variants: (A) an out-of-memory process kill when r=2147483647 forces a ~16 GB allocation attempt, and (B) a runtime panic via out-of-bounds slice indexing when r=-1. Any service that opens attacker-supplied XLSX files and calls GetCellValue is affected. No authentication is required. This issue is fixed in version 2.11.0.
CVE-2026-54063
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 57% 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
- 7.5
- EG Score
- 7.5(medium)
- EPSS
- 43.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026Unbounded Row Index Allocation in Worksheet Parser (checkSheet OOM/Panic DoS) · Advisory · qax-os/excelize · GitHub
https://github.com/qax-os/excelize/security/advisories/GHSA-h69g-9hx6-f3v4v2.11.0
Patch available: qax-os/excelize v2.11.0
https://github.com/qax-os/excelize/releases/tag/v2.11.0Vendor Advisories for CVE-2026-54063(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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 11:59 UTCEG score recompute
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 00:46 UTCEG score recompute
- 2026-07-12 13:29 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 02:15 UTCEG score recompute
- 2026-07-11 15:01 UTCEG score recompute
- 2026-07-11 03:47 UTCEG score recompute
- 2026-07-10 16:33 UTCEG score recompute
- 2026-07-10 16:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-54063?
When was CVE-2026-54063 disclosed?
Is CVE-2026-54063 actively exploited?
What is the CVSS score of CVE-2026-54063?
How do I remediate CVE-2026-54063?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54063
Is Your Infrastructure Affected by CVE-2026-54063?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.