CVE-2026-128342
Exceljs Project Exceljs ≤ 4.4.0
Raw vector
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/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-128342 is a high-severity Unchecked Input for Loop Condition (CWE-606) vulnerability in Exceljs Project Exceljs. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 46th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-125157
Vulnerability Data
ExcelJS through 4.4.0 contains a denial of service vulnerability that allows attackers to block the event loop by supplying an unbounded sheetId in xl/workbook.xml. Attackers can provide a workbook with a huge sheetId, making the sparse worksheet array walk stall…
more
worksheets, getWorksheet and writeBuffer for seconds.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.3.2
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Input validation directly stops untrusted values from reaching loop conditions without bounds or sanity checks.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent unchecked loop conditions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing in development can detect and block unchecked loop conditions before release.
Training developers in secure coding practices helps them recognize and validate loop-condition inputs, but the effect is a minority one because the practice is fallible and a different clause (e.g. A.8.29 security testing) carries the stronger preventive effect, mirroring the A.8.28 -> CWE-502 anchor.
Secure coding standards directly mandate validation of loop-control inputs to prevent unbounded iteration.
A.8.8's reach is DISCLOSURE-based (vendor advisories, CVE feeds, scanning of deployed components), so it finds CWE-606 only where the weakness surfaces as a published CVE in a third-party component (e.g., CVE-2025-32399 in a Profinet library); the majority of CWE-606 instances are first-party implementation defects invisible to disclosure-based scanning, leaving a nameable remainder outside the control's reach.