CVE-2026-83607

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, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. 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, github_pr, github_commit, github_release.
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

Element name injection via createElement() bypasses requireWellFormed · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-w2rr-34g9-rvrj

Vendor Advisories for CVE-2026-83607(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 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.10-1 ... 0.9.9-1 (7 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 25× in last 7d / 50× 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-18 23:01 UTCEG score recompute
  2. 2026-09-18 23:01 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 09:52 UTCVendor advisory
  5. 2026-09-17 20:44 UTCEG score recompute
  6. 2026-09-17 20:44 UTCVendor advisory
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 03:11 UTCEG score recompute
  9. 2026-09-17 03:11 UTCVendor advisory
  10. 2026-09-16 14:09 UTCEPSS rescore
  11. 2026-09-16 14:02 UTCEG score recompute
  12. 2026-09-16 14:02 UTCVendor advisory
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 00:15 UTCVendor advisory
  15. 2026-09-15 11:06 UTCEG score recompute
  16. 2026-09-15 11:06 UTCVendor advisory
  17. 2026-09-15 03:12 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-14 21:58 UTCVendor advisory
  20. 2026-09-14 08:48 UTCVendor advisory
  21. 2026-09-13 19:40 UTCEG score recompute
  22. 2026-09-13 19:40 UTCVendor advisory
  23. 2026-09-13 06:31 UTCVendor advisory
  24. 2026-09-12 17:22 UTCEG score recompute
  25. 2026-09-12 17:22 UTCVendor advisory
Show 25 more
  1. 2026-09-12 04:14 UTCVendor advisory
  2. 2026-09-11 15:06 UTCEG score recompute
  3. 2026-09-11 15:06 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-10 12:49 UTCEG score recompute
  7. 2026-09-09 10:32 UTCEG score recompute
  8. 2026-09-09 10:32 UTCVendor advisory
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-08 07:42 UTCVendor advisory
  11. 2026-09-07 18:34 UTCEG score recompute
  12. 2026-09-07 18:34 UTCVendor advisory
  13. 2026-09-06 16:10 UTCEG score recompute
  14. 2026-09-06 13:48 UTCEPSS rescore
  15. 2026-09-06 02:58 UTCEG score recompute
  16. 2026-09-05 15:31 UTCEPSS rescore
  17. 2026-09-05 00:39 UTCEG score recompute
  18. 2026-09-04 11:31 UTCEG score recompute
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-02 20:00 UTCEG score recompute
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 16:25 UTCEG score recompute
  23. 2026-09-01 15:40 UTCEG score recompute
  24. 2026-09-01 14:34 UTCEG score recompute
  25. 2026-09-01 14:33 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-83607?
CVE-2026-83607 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, Document.createElement(tagName) stores an unvalidated element name and…
When was CVE-2026-83607 disclosed?
CVE-2026-83607 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-83607 actively exploited?
CVE-2026-83607 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-83607?
CVE-2026-83607 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-83607?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83607, 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-83607

Explore →

Is Your Infrastructure Affected by CVE-2026-83607?

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

Start Free Scan →Browse All CVEs