Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

xmldom: Quadratic-time attribute deduplication

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-83613

Published

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.

Source published
1 Sep 2026 14:38:49 UTC
Source modified
4 Sep 2026 01:57:57 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · 8.7 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

euvd · EUVD-2026-69231

Published

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 1, 2026, 2:38:49 PM

dateUpdated: Sep 4, 2026, 1:57:57 AM

5 related source bulletins · separate from aliases

NCSC-2026-0431: Kwetsbaarheden verholpen in IBM DataPower Gateway en onderliggende componenten

CVE-2023-53781 · CVE-2025-14087 · CVE-2025-14512 · CVE-2025-21858 · CVE-2025-22105 · CVE-2025-37980 · CVE-2025-38015 · CVE-2025-38097 · CVE-2025-38180 · CVE-2025-38400 · CVE-2025-38405 · CVE-2025-38441 · CVE-2025-38470 · CVE-2025-38653 · CVE-2025-39766 · CVE-2025-39797 · CVE-2025-39866 · CVE-2025-40134 · CVE-2025-48431 · CVE-2025-5278 · CVE-2025-68183 · CVE-2025-68211 · CVE-2025-68214 · CVE-2025-68347 · CVE-2025-68366 · CVE-2025-68724 · CVE-2025-71066 · CVE-2025-71089 · CVE-2026-12143 · CVE-2026-13257 · CVE-2026-13258 · CVE-2026-13757 · CVE-2026-14269 · CVE-2026-14273 · CVE-2026-14496 · CVE-2026-14497 · CVE-2026-14502 · CVE-2026-14507 · CVE-2026-14508 · CVE-2026-14509 · CVE-2026-14888 · CVE-2026-14905 · CVE-2026-14988 · CVE-2026-14990 · CVE-2026-14991 · CVE-2026-14992 · CVE-2026-14999 · CVE-2026-15588 · CVE-2026-15762 · CVE-2026-15781 · CVE-2026-15784 · CVE-2026-15819 · CVE-2026-15822 · CVE-2026-15824 · CVE-2026-16111 · CVE-2026-16159 · CVE-2026-16161 · CVE-2026-16163 · CVE-2026-16164 · CVE-2026-16165 · CVE-2026-16167 · CVE-2026-16169 · CVE-2026-16170 · CVE-2026-16176 · CVE-2026-16177 · CVE-2026-16178 · CVE-2026-16179 · CVE-2026-16181 · CVE-2026-16182 · CVE-2026-16340 · CVE-2026-16439 · CVE-2026-16440 · CVE-2026-16441 · CVE-2026-2100 · CVE-2026-22979 · CVE-2026-22984 · CVE-2026-22990 · CVE-2026-23002 · CVE-2026-23060 · CVE-2026-23110 · CVE-2026-23204 · CVE-2026-23209 · CVE-2026-23216 · CVE-2026-23243 · CVE-2026-23270 · CVE-2026-23392 · CVE-2026-23455 · CVE-2026-2391 · CVE-2026-31411 · CVE-2026-31419 · CVE-2026-31488 · CVE-2026-31508 · CVE-2026-31532 · CVE-2026-31581 · CVE-2026-31607 · CVE-2026-31613 · CVE-2026-31669 · CVE-2026-31677 · CVE-2026-31684 · CVE-2026-31685 · CVE-2026-33845 · CVE-2026-33846 · CVE-2026-3832 · CVE-2026-3833 · CVE-2026-4046 · CVE-2026-41254 · CVE-2026-41602 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-42009 · CVE-2026-42010 · CVE-2026-42011 · CVE-2026-42012 · CVE-2026-42013 · CVE-2026-42014 · CVE-2026-42015 · CVE-2026-43027 · CVE-2026-43037 · CVE-2026-43038 · CVE-2026-43056 · CVE-2026-43074 · CVE-2026-43116 · CVE-2026-43125 · CVE-2026-43163 · CVE-2026-43190 · CVE-2026-43198 · CVE-2026-43260 · CVE-2026-43284 · CVE-2026-43303 · CVE-2026-43329 · CVE-2026-43499 · CVE-2026-43501 · CVE-2026-43868 · CVE-2026-43870 · CVE-2026-4437 · CVE-2026-4438 · CVE-2026-45852 · CVE-2026-46054 · CVE-2026-46086 · CVE-2026-46116 · CVE-2026-46173 · CVE-2026-46181 · CVE-2026-46242 · CVE-2026-46259 · CVE-2026-46300 · CVE-2026-46331 · CVE-2026-46333 · CVE-2026-46917 · CVE-2026-46968 · CVE-2026-47010 · CVE-2026-47021 · CVE-2026-47027 · CVE-2026-47059 · CVE-2026-47063 · CVE-2026-48144 · CVE-2026-48145 · CVE-2026-5260 · CVE-2026-52923 · CVE-2026-52991 · CVE-2026-53006 · CVE-2026-53009 · CVE-2026-53131 · CVE-2026-53189 · CVE-2026-53264 · CVE-2026-53266 · CVE-2026-5419 · CVE-2026-5450 · CVE-2026-55602 · CVE-2026-55603 · CVE-2026-55968 · CVE-2026-55970 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58662 · CVE-2026-59879 · CVE-2026-59880 · CVE-2026-60147 · CVE-2026-60589 · CVE-2026-61308 · CVE-2026-63913 · CVE-2026-63952 · CVE-2026-64017 · CVE-2026-64530 · CVE-2026-64560 · CVE-2026-70906 · CVE-2026-70907 · CVE-2026-74581 · CVE-2026-82417 · CVE-2026-82562 · CVE-2026-83605 · CVE-2026-83607 · CVE-2026-83608 · CVE-2026-83613 · CVE-2026-83614 · CVE-2026-83615 · CVE-2026-83616 · CVE-2026-83619

RHSA-2026:69248: Red Hat Security Advisory: Red Hat Developer Hub 1.9.9 release.

CVE-2026-19534 · CVE-2026-33818 · CVE-2026-54272 · CVE-2026-55553 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-67214 · CVE-2026-67312 · CVE-2026-67422 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-83605 · CVE-2026-83607 · CVE-2026-83608 · CVE-2026-83613 · CVE-2026-83614 · CVE-2026-83615 · CVE-2026-83616 · CVE-2026-83619 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-84961

WID-SEC-W-2026-3596: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2022-35948 · CVE-2026-13149 · CVE-2026-14257 · CVE-2026-15157 · CVE-2026-1527 · CVE-2026-16728 · CVE-2026-16729 · CVE-2026-18149 · CVE-2026-18540 · CVE-2026-19534 · CVE-2026-2391 · CVE-2026-45820 · CVE-2026-54272 · CVE-2026-63670 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-69198 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-77037 · CVE-2026-77063 · CVE-2026-77078 · CVE-2026-82333 · CVE-2026-82417 · CVE-2026-82562 · CVE-2026-83605 · CVE-2026-83606 · CVE-2026-83607 · CVE-2026-83608 · CVE-2026-83609 · CVE-2026-83610 · CVE-2026-83611 · CVE-2026-83612 · CVE-2026-83613 · CVE-2026-83614 · CVE-2026-83615 · CVE-2026-83616 · CVE-2026-83618 · CVE-2026-83619 · CVE-2026-84292 · CVE-2026-84371 · CVE-2026-84375 · CVE-2026-84890 · CVE-2026-84933 · CVE-2026-84947 · CVE-2026-84961 · CVE-2026-85008 · CVE-2026-85014 · CVE-2026-85024 · CVE-2026-85152

msrc_CVE-2026-83613: xmldom: Quadratic-time attribute deduplication

CVE-2026-83613

WID-SEC-W-2026-3623: IBM DataPower Gateway: Mehrere Schwachstellen

CVE-2023-53781 · CVE-2025-14087 · CVE-2025-14512 · CVE-2025-21858 · CVE-2025-22105 · CVE-2025-37980 · CVE-2025-38015 · CVE-2025-38097 · CVE-2025-38180 · CVE-2025-38400 · CVE-2025-38405 · CVE-2025-38441 · CVE-2025-38470 · CVE-2025-38653 · CVE-2025-39766 · CVE-2025-39797 · CVE-2025-39866 · CVE-2025-40134 · CVE-2025-48431 · CVE-2025-5278 · CVE-2025-68183 · CVE-2025-68211 · CVE-2025-68214 · CVE-2025-68347 · CVE-2025-68366 · CVE-2025-68724 · CVE-2025-71066 · CVE-2025-71089 · CVE-2026-12143 · CVE-2026-13257 · CVE-2026-13258 · CVE-2026-13757 · CVE-2026-14269 · CVE-2026-14273 · CVE-2026-14496 · CVE-2026-14497 · CVE-2026-14502 · CVE-2026-14507 · CVE-2026-14508 · CVE-2026-14509 · CVE-2026-14888 · CVE-2026-14905 · CVE-2026-14988 · CVE-2026-14990 · CVE-2026-14991 · CVE-2026-14992 · CVE-2026-14999 · CVE-2026-15588 · CVE-2026-15762 · CVE-2026-15781 · CVE-2026-15784 · CVE-2026-15819 · CVE-2026-15822 · CVE-2026-15824 · CVE-2026-16111 · CVE-2026-16159 · CVE-2026-16161 · CVE-2026-16163 · CVE-2026-16164 · CVE-2026-16165 · CVE-2026-16167 · CVE-2026-16169 · CVE-2026-16170 · CVE-2026-16176 · CVE-2026-16177 · CVE-2026-16178 · CVE-2026-16179 · CVE-2026-16181 · CVE-2026-16182 · CVE-2026-16340 · CVE-2026-16439 · CVE-2026-16440 · CVE-2026-16441 · CVE-2026-2100 · CVE-2026-22979 · CVE-2026-22984 · CVE-2026-22990 · CVE-2026-23002 · CVE-2026-23060 · CVE-2026-23110 · CVE-2026-23204 · CVE-2026-23209 · CVE-2026-23216 · CVE-2026-23243 · CVE-2026-23270 · CVE-2026-23392 · CVE-2026-23455 · CVE-2026-2391 · CVE-2026-31411 · CVE-2026-31419 · CVE-2026-31488 · CVE-2026-31508 · CVE-2026-31532 · CVE-2026-31581 · CVE-2026-31607 · CVE-2026-31613 · CVE-2026-31669 · CVE-2026-31677 · CVE-2026-31684 · CVE-2026-31685 · CVE-2026-33845 · CVE-2026-33846 · CVE-2026-3832 · CVE-2026-3833 · CVE-2026-4046 · CVE-2026-41254 · CVE-2026-41602 · CVE-2026-41606 · CVE-2026-41607 · CVE-2026-42009 · CVE-2026-42010 · CVE-2026-42011 · CVE-2026-42012 · CVE-2026-42013 · CVE-2026-42014 · CVE-2026-42015 · CVE-2026-43027 · CVE-2026-43037 · CVE-2026-43038 · CVE-2026-43056 · CVE-2026-43074 · CVE-2026-43116 · CVE-2026-43125 · CVE-2026-43163 · CVE-2026-43190 · CVE-2026-43198 · CVE-2026-43260 · CVE-2026-43284 · CVE-2026-43303 · CVE-2026-43329 · CVE-2026-43499 · CVE-2026-43501 · CVE-2026-43868 · CVE-2026-43870 · CVE-2026-4437 · CVE-2026-4438 · CVE-2026-45852 · CVE-2026-46054 · CVE-2026-46086 · CVE-2026-46116 · CVE-2026-46173 · CVE-2026-46181 · CVE-2026-46242 · CVE-2026-46259 · CVE-2026-46300 · CVE-2026-46331 · CVE-2026-46333 · CVE-2026-46917 · CVE-2026-46968 · CVE-2026-47010 · CVE-2026-47021 · CVE-2026-47027 · CVE-2026-47059 · CVE-2026-47063 · CVE-2026-48144 · CVE-2026-48145 · CVE-2026-5260 · CVE-2026-52923 · CVE-2026-52991 · CVE-2026-53006 · CVE-2026-53009 · CVE-2026-53131 · CVE-2026-53189 · CVE-2026-53264 · CVE-2026-53266 · CVE-2026-5419 · CVE-2026-5450 · CVE-2026-55602 · CVE-2026-55603 · CVE-2026-55968 · CVE-2026-55970 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58016 · CVE-2026-58662 · CVE-2026-59879 · CVE-2026-59880 · CVE-2026-60147 · CVE-2026-60589 · CVE-2026-61308 · CVE-2026-63913 · CVE-2026-63952 · CVE-2026-64017 · CVE-2026-64530 · CVE-2026-64560 · CVE-2026-70906 · CVE-2026-70907 · CVE-2026-74581 · CVE-2026-82417 · CVE-2026-82562 · CVE-2026-83605 · CVE-2026-83607 · CVE-2026-83608 · CVE-2026-83613 · CVE-2026-83614 · CVE-2026-83615 · CVE-2026-83616 · CVE-2026-83619

Source published
Sep 1, 2026, 2:38:49 PM (timezone not stated)
Source modified
Sep 4, 2026, 1:57:57 AM (timezone not stated)
Saved here
17 Nov 2026 19:30:53 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 4.0 · 8.7 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

nvd · CVE-2026-83613

Published

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-407

Original publisher date fields

published: 2026-09-01T15:17:39.583

lastModified: 2026-09-08T21:11:31.703

Source published
1 Sep 2026 15:17:39 UTC
Source modified
8 Sep 2026 21:11:31 UTC
Saved here
25 Oct 2026 16:19:10 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 4.0 · [email protected] · Secondary · 8.7 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:X

osv · GHSA-8344-3jmq-59r6

Published

## Summary xmldom builds the attribute collection of every parsed element by inserting attributes one at a time into a DOM `NamedNodeMap`. Each insertion first performs a **linear scan of all already-inserted attributes** to enforce the DOM uniqueness rule (no two attributes with the same qualified name / namespace+local-name). Parsing an element that carries `M` distinct attributes therefore costs `1 + 2 + … + M = O(M²)` comparisons. Because the trigger is simply "one element with many attributes", the attack payload is a **fully well-formed XML document**. No malformed markup, no error recovery, and no non-default parser options are involved — parsing completes silently with zero `warning`/`error`/`fatalError` events. An attacker who can submit a modest, highly compressible document (a single element with tens of thousands of attributes, ~340 KB uncompressed) can consume seconds of single-threaded CPU per request, enabling an unauthenticated denial of service. This is distinct from the known quadratic-**memory** namespace-map issue: it burns **CPU** and it does not require any namespace declarations or nesting. ## Details The DOM content handler adds each attribute of a starting element by calling `el.setAttributeNode(attr)` in a loop: ```js // DOMHandler.startElement for (var i = 0; i < len; i++) { var namespaceURI = attrs.getURI(i); var value = attrs.getValue(i); var qName = attrs.getQName(i); var attr = doc.createAttributeNS(namespaceURI, qName); attr.value = attr.nodeValue = value; el.setAttributeNode(attr); // O(existing attrs) each — see below } ``` https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom-parser.js#L370-L387 `setAttributeNode` delegates to `NamedNodeMap.setNamedItem`, which calls `getNamedItemNS` to look for an existing attribute with the same namespace URI and local name before appending: ```js setNamedItem: function (attr) { var el = attr.ownerElement; if (el && el !== this._ownerElement) { throw new DOMException(DOMException.INUSE_ATTRIBUTE_ERR); } var oldAttr = this.getNamedItemNS(attr.namespaceURI, attr.localName); // linear scan if (oldAttr === attr) { return attr; } _addNamedNode(this._ownerElement, this, attr, oldAttr); return oldAttr; }, ``` https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L612-L623 `getNamedItemNS` walks the whole list on every call: ```js getNamedItemNS: function (namespaceURI, localName) { if (!namespaceURI) { namespaceURI = null; } var i = 0; while (i < this.length) { var node = this[i]; if (node.localName === localName && node.namespaceURI === namespaceURI) { return node; } i++; } return null; }, ``` https://github.com/xmldom/xmldom/blob/bb7a085dc5ba1eea3212388509b97bb4b4af32b9/lib/dom.js#L702-L715 For the i-th attribute the scan visits `i-1` entries, so inserting `M` distinct attributes performs `Θ(M²)` comparisons. There is no hash index or set keyed by name; the map is a plain array-backed structure. The same structure exists on 0.8.x. There `setNamedItem` dedups via `getNamedItem(attr.nodeName)` instead of `getNamedItemNS`, but that method is likewise a full linear scan, so the complexity is identical: - `startElement` loop / `setAttributeNode`: https://github.com/xmldom/xmldom/blob/e5c14802592685bb872c042c54c3f73758875c85/lib/dom-parser.js#L159-L176 - `setNamedItem` → linear `getNamedItem`: https://github.com/xmldom/xmldom/blob/e5c14802592685bb872c042c54c3f73758875c85/lib/dom.js#L286-L308 The linear-scan `NamedNodeMap` predates the `@xmldom/xmldom` fork and is present unchanged in the unscoped `xmldom` package back to its earliest published release. In `[email protected]`, parsing already inserts each attribute one at a time (`DOMHandler.startElement` loops calling `setAttributeNS` → `setAttributeNode` → `NamedNodeMap.setNamedItem`), and `setNamedItem` dedups by calling `getNamedItemNS`, which is a full linear `while (i--)` scan of the already-inserted attributes — the identical `O(M²)` structure. The whole unscoped line (`0.1.0` … `0.6.0`) is therefore affected; the earliest published tag (`0.1.0`) was verified to contain the per-insert linear dedup scan. ## Proof of Concept A single well-formed element with `M` distinct attributes. No malformed markup and no options: ```js 'use strict'; var DOMParser = require('@xmldom/xmldom').DOMParser; function buildDoc(m) { var parts = new Array(m); for (var i = 0; i < m; i++) parts[i] = 'a' + i + '="x"'; return '<r ' + parts.join(' ') + '/>'; // <r a0="x" a1="x" ... a{M-1}="x"/> } for (var _i = 0, sizes = [2000, 4000, 8000, 16000, 32000]; _i < sizes.length; _i++) { var m = sizes[_i]; var xml = buildDoc(m); var t0 = process.hrtime.bigint(); var doc = new DOMParser().parseFromString(xml, 'text/xml'); // silent: no error events var ms = Number(process.hrtime.bigint() - t0) / 1e6; console.log(m + ' attrs, ' + xml.length + ' bytes -> ' + ms.toFixed(1) + ' ms; parsed=' + doc.documentElement.attributes.length); } ``` Measured with Node.js v18.20.8 (wall-clock; absolute numbers vary by host, the **scaling** is the load-bearing fact): **`@xmldom/xmldom` 0.9.10:** | M (attributes) | input bytes | time (ms) | ratio vs prev | |---:|---:|---:|---:| | 2000 | 18,894 | 13.4 | — | | 4000 | 38,894 | 38.7 | ×2.9 | | 8000 | 78,894 | 100.8 | ×2.6 | | 16000 | 164,894 | 406.2 | ×4.0 | | 32000 | 340,894 | 2149.5 | ×5.3 | **`@xmldom/xmldom` 0.8.13:** | M (attributes) | input bytes | time (ms) | |---:|---:|---:| | 2000 | 18,894 | 10.6 | | 4000 | 38,894 | 19.9 | | 8000 | 78,894 | 75.9 | | 16000 | 164,894 | 657.7 | | 32000 | 340,894 | 1643.2 | **`xmldom` (unscoped) 0.6.0:** 4000 → 28.2 ms, 8000 → 131.8 ms, 16000 → 545.2 ms (≈ ×4 per doubling). Time grows ≈ ×4 per doubling of `M` — quadratic. About **340 KB of well-formed input costs ~1.6–2.1 s of single-threaded CPU**, and it keeps scaling: doubling the attribute count quadruples the cost. The document is trivially generated and compresses to a few kilobytes on the wire. ## Impact Unauthenticated, remotely triggerable denial of service against any service that parses attacker-influenced XML/HTML with xmldom. A single request holds one event-loop thread for seconds; a handful of concurrent requests can saturate CPU and stall the process. Because the payload is a plain well-formed document (one element, many attributes), it passes any "must be well-formed" gate and reaches the parser before any application-level validation (e.g. schema checks or signature verification) can run. The payload is highly compressible, so it is effective over compressed transports. ## Fix Applied Replaced the per-insert linear duplicate scan on the parse-time dedup path with a name-keyed index, so de-duplicating an element's attributes during parse is O(M) instead of O(M²) — a well-formed-but-hostile attribute list can no longer wedge the parse. Behavior-preserving: attribute order and duplicate resolution (last value wins, first position kept) are byte-identical. Non-breaking and independent of `requireWellFormed`; ships on both maintained versions.

Source published
8 Sep 2026 21:01:31 UTC
Source modified
8 Sep 2026 21:25:58 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V4 · 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

Publisher rating · HIGH

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 09:42 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current