NVD published 1 Sep 2026
CVE-2026-83613
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, DOMHandler.startElement in lib/dom-parser.js inserts every parsed attribute through setAttributeNode, while NamedNodeMap.setNamedItem in lib/dom.js calls the linear getNamedItem or getNamedItemNS lookup for each insertion. A well-formed element with many distinct attributes therefore requires quadratic comparisons during DOMParser.parseFromString() and can stall a Node.js event loop before application validation. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
Signals
- KEV, exploited in the wild
- no
- EPSS, 30-day forecast
- 0.6%, 50th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety. No score published by NVD.
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 1 dispatch
Public exploit code none in our sources
No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.