CVE-2026-83613

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (7)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Release 0.9.12 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12

https://github.com/xmldom/xmldom/releases/tag/0.9.12
github_release Patch Available

Release 0.8.15 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15

https://github.com/xmldom/xmldom/releases/tag/0.8.15
github_commit Patch Available

commit cfb09b5dbeb0 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12 (contains commit cfb09b5dbeb0)

https://github.com/xmldom/xmldom/commit/cfb09b5dbeb035fdfedc9f01e2bbaf226bf47cf3
github_commit Patch Available

commit 2c548f200cfe (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit 2c548f200cfe)

https://github.com/xmldom/xmldom/commit/2c548f200cfec991cd5846627ef8f03542309213
github_pr Patch Available

Backport security release 0.8.15 — parser/DOM DoS, serializer name checks, end-tag reporting

Patch available: xmldom/xmldom 0.8.15 (PR #1072 merged 2026-08-21)

https://github.com/xmldom/xmldom/pull/1072
github_pr Patch Available

Security release 0.9.12 — parser/DOM DoS, serializer name checks, multiline-anchor bypass

Patch available: xmldom/xmldom 0.9.12 (PR #1071 merged 2026-08-21)

https://github.com/xmldom/xmldom/pull/1071
github Patch Available🟡 PoC Available

Quadratic-time attribute deduplication in xmldom (CWE-407) · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-8344-3jmq-59r6

Vendor Advisories for CVE-2026-83613(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
npm(2)
PackageVulnerable rangeFixed inDependents
xmldom———
@xmldom/xmldom—0.9.12—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.8.6-1 ... 0.9.9-1 (10 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.10-1 ... 0.9.9-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.10-1 ... 0.9.9-1 (7 versions)0.9.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 26× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 00:54 UTCEG score recompute
  2. 2026-09-19 00:54 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 13:31 UTCVendor advisory
  5. 2026-09-18 02:09 UTCEG score recompute
  6. 2026-09-18 02:09 UTCVendor advisory
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 14:46 UTCVendor advisory
  9. 2026-09-17 03:22 UTCVendor advisory
  10. 2026-09-16 15:59 UTCEG score recompute
  11. 2026-09-16 15:59 UTCVendor advisory
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 04:37 UTCVendor advisory
  15. 2026-09-15 17:14 UTCVendor advisory
  16. 2026-09-15 05:52 UTCEG score recompute
  17. 2026-09-15 05:52 UTCVendor advisory
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 18:29 UTCVendor advisory
  21. 2026-09-14 07:05 UTCVendor advisory
  22. 2026-09-13 19:42 UTCEG score recompute
  23. 2026-09-13 19:42 UTCVendor advisory
  24. 2026-09-13 08:19 UTCVendor advisory
  25. 2026-09-12 20:57 UTCEG score recompute
Show 30 more
  1. 2026-09-12 20:57 UTCVendor advisory
  2. 2026-09-12 09:35 UTCVendor advisory
  3. 2026-09-11 22:12 UTCEG score recompute
  4. 2026-09-11 22:12 UTCVendor advisory
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 10:48 UTCEG score recompute
  8. 2026-09-11 10:48 UTCVendor advisory
  9. 2026-09-10 11:36 UTCEG score recompute
  10. 2026-09-09 08:35 UTCEG score recompute
  11. 2026-09-09 08:35 UTCVendor advisory
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 10:02 UTCVendor advisory
  14. 2026-09-07 21:39 UTCEG score recompute
  15. 2026-09-07 21:39 UTCVendor advisory
  16. 2026-09-07 10:17 UTCVendor advisory
  17. 2026-09-06 22:54 UTCEG score recompute
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-06 00:08 UTCEG score recompute
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-05 01:18 UTCEG score recompute
  22. 2026-09-04 13:52 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-04 02:28 UTCEG score recompute
  25. 2026-09-04 02:04 UTCEG score recompute
  26. 2026-09-02 14:34 UTCEG score recompute
  27. 2026-09-02 14:12 UTCEPSS rescore
  28. 2026-09-01 15:40 UTCEG score recompute
  29. 2026-09-01 14:44 UTCEG score recompute
  30. 2026-09-01 14:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83613?
CVE-2026-83613 is a high vulnerability published on September 1, 2026. 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…
When was CVE-2026-83613 disclosed?
CVE-2026-83613 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-83613 actively exploited?
CVE-2026-83613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-83613?
CVE-2026-83613 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-83613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-83613

Explore →

Is Your Infrastructure Affected by CVE-2026-83613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs