CVE-2026-83605

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.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the attribute name, while Document.createAttribute(name) validates against QName. XMLSerializer.serializeToString() emits attribute names verbatim, and requireWellFormed: true did not validate them, so a crafted name can terminate the intended attribute and inject additional attributes, including event handlers, into browser-consumed output; synthesized xmlns:PREFIX declarations expose the same unchecked-name boundary. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; 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_pr, github_commit, github_release, github.
github_release Patch Available

Release 0.9.11 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.11

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

Release 0.8.14 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.14

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

commit d8212e632507 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.14 (contains commit d8212e632507)

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

commit cba1321218b0 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.11 (contains commit cba1321218b0)

https://github.com/xmldom/xmldom/commit/cba1321218b069182695813fa7565653708e172e
github_pr Patch Available

fix: reject invalid element and attribute names when requireWellFormed

Patch available: xmldom/xmldom 0.8.14 (PR #1050 merged 2026-08-12)

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

fix: reject invalid element and attribute names when requireWellFormed

Patch available: xmldom/xmldom 0.9.11 (PR #1043 merged 2026-08-12)

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

Attribute name injection via setAttribute() bypasses requireWellFormed · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-4w3w-2rp5-g8jm

Vendor Advisories for CVE-2026-83605(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.8.14—
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 (6 versions)0.9.11-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 52× 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 04:03 UTCEG score recompute
  2. 2026-09-19 04:03 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 15:06 UTCVendor advisory
  5. 2026-09-18 02:05 UTCEG score recompute
  6. 2026-09-18 02:05 UTCVendor advisory
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 13:07 UTCVendor advisory
  9. 2026-09-17 00:09 UTCEG score recompute
  10. 2026-09-17 00:09 UTCVendor advisory
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 11:11 UTCEG score recompute
  13. 2026-09-16 11:11 UTCVendor advisory
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 22:14 UTCVendor advisory
  16. 2026-09-15 09:15 UTCEG score recompute
  17. 2026-09-15 09:15 UTCVendor advisory
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 20:17 UTCVendor advisory
  21. 2026-09-14 07:20 UTCVendor advisory
  22. 2026-09-13 18:22 UTCEG score recompute
  23. 2026-09-13 18:22 UTCVendor advisory
  24. 2026-09-13 05:24 UTCVendor advisory
  25. 2026-09-12 16:26 UTCEG score recompute
Show 27 more
  1. 2026-09-12 16:26 UTCVendor advisory
  2. 2026-09-12 03:29 UTCEG score recompute
  3. 2026-09-12 03:29 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 14:31 UTCEG score recompute
  7. 2026-09-10 12:36 UTCEG score recompute
  8. 2026-09-09 10:10 UTCEG score recompute
  9. 2026-09-09 10:10 UTCVendor advisory
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-08 03:53 UTCEG score recompute
  12. 2026-09-08 03:53 UTCVendor advisory
  13. 2026-09-07 14:55 UTCVendor advisory
  14. 2026-09-07 00:37 UTCEG score recompute
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-05 22:41 UTCEG score recompute
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 20:46 UTCEG score recompute
  19. 2026-09-04 07:43 UTCEG score recompute
  20. 2026-09-04 05:07 UTCEPSS rescore
  21. 2026-09-03 18:45 UTCEG score recompute
  22. 2026-09-03 17:39 UTCEG score recompute
  23. 2026-09-02 20:00 UTCEG score recompute
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 15:40 UTCEG score recompute
  26. 2026-09-01 14:27 UTCEG score recompute
  27. 2026-09-01 14:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83605?
CVE-2026-83605 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.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the…
When was CVE-2026-83605 disclosed?
CVE-2026-83605 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-83605 actively exploited?
CVE-2026-83605 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 71.5% of all scored CVEs.
What is the CVSS score of CVE-2026-83605?
CVE-2026-83605 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-83605?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83605, 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-83605

Explore →

Is Your Infrastructure Affected by CVE-2026-83605?

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

Start Free Scan →Browse All CVEs