Cyber Resilience

CVE-2026-59162

Excelize ≤ 2.11.0

Public PoC
Published
10 July 2026
Modified
16 July 2026
Patch / advisory
View advisory
CVSS Score v4 6.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0039 32th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2026-59162 is a medium-severity Uncaught Exception (CWE-248) vulnerability in Excelize Excelize. Its CVSS base score is 6.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 32th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

Excelize is a Go language library for reading and writing Microsoft Excel spreadsheets. Prior to 2.11.0, Excelize parses shared-string cell values with strconv.Atoi and checks only the upper bound before indexing the shared string slice, allowing an XLSX file containing…

more

a shared-string cell with -1 to trigger sharedStrings[-1] and panic when read through GetCellValue or GetRows. This issue is fixed in version 2.11.0.

CWE(s)
CWE-248CWE-755

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1489 Service Stop Impact
Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-59161Same product: Excelize Excelize
CVE-2026-54063Same product: Excelize Excelize
CVE-2023-23774Shared CWE-248, CWE-755
CVE-2026-62994Shared CWE-248, CWE-755
CVE-2024-23325Shared CWE-248, CWE-755
CVE-2023-29520Shared CWE-248, CWE-755
CVE-2026-42545Shared CWE-248, CWE-755
CVE-2023-22292Shared CWE-248, CWE-755
CVE-2023-3774Shared CWE-248, CWE-755
CVE-2026-54775Shared CWE-248, CWE-755

Affected Assets

excelize
excelize
≤ 2.11.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-24 Fail in Known State good match

Requires the system to fail to a known safe state on specified failures, limiting the impact of unhandled exceptional conditions.

SI-17 Fail-safe Procedures good match

Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled or mishandled exceptional conditions.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles include robust exception management to keep the system in a defined state.

SI-11 Error Handling partial match

Error handling requirements force structured catching and response to exceptions instead of allowing them to propagate uncaught.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require structured exception handling to prevent uncaught exceptions from reaching production.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect uncaught exceptions before production deployment.

A.5.37 Documented operating procedures partial match
degrades

Documented operating procedures may specify exception handling but do not guarantee implementation.

A.8.15 Logging partial match
finds

Logging captures unhandled exceptions, aiding detection but not preventing the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring can surface unhandled exceptions but does not enforce proper handling.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle includes exception-handling standards that reduce uncaught exceptions.

A.8.26 Application security requirements partial match
prevents

Application security requirements typically mandate robust error and exception handling.

References