CVE-2026-59161
DoS via crafted XLSX causing excessive memory/CPU in Excelize (<2.11.0).
Is CVE-2026-59161 being exploited?
Not confirmed. CVE-2026-59161 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-59161?
CVE-2026-59161 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59161?
Yes. A fix has been recorded for CVE-2026-59161. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59161 affect?
CVE-2026-59161 affects Excelize < 2.11.0, Go applications using excelize Rows/GetRows streaming reader, Services that accept untrusted XLSX uploads. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59161?
Upgrade to excelize v2.11.0+, validate/sandbox XLSX inputs and limit resource usage.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Processing a malicious XLSX with out‑of‑range row index causes Excelize to allocate/appended empty rows, exhausting memory/CPU and causing application crash/DoS.
Patch when possible
- affected< 2.11.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.