CVE-2026-128337
Exceljs Project Exceljs ≤ 4.4.0
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/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: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-128337 is a high-severity Prototype Pollution (CWE-1321) vulnerability in Exceljs Project Exceljs. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-125040
Vulnerability Data
ExcelJS through 4.4.0 contains a prototype pollution vulnerability in mergeConditionalFormattings that allows attackers to modify Object.prototype by supplying an x14:cfRule id of __proto__. Attackers can craft an xlsx file that, when loaded with xlsx.load(), sets properties such as type, direction,…
more
border and cfvo on every object in the process until it restarts.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.3.6
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 safe property assignment to prevent prototype pollution.
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 catches prototype-pollution flaws before release.
Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.
A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; prototype pollution is such a weakness, but the clause's ceiling on `prevents` is `partial` because the effect depends on the supplier's implementation of secure coding and testing.
Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. Prototype pollution does commonly surface as CVEs in third-party libraries (lodash, jQuery, etc., as the observed examples show), so A.8.8 finds those. But most prototype pollution lives in first-party JavaScript code that nobody publishes an advisory about, and that share is invisible to A.8.8's disclosure-based programme — the same scope seam that put A.8.8 -> CWE-89 at `partial`.