CVE-2026-83608

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, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. 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_release, github, github_pr, github_commit.
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 85f12eb4d14b (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit 85f12eb4d14b)

https://github.com/xmldom/xmldom/commit/85f12eb4d14b44de33216cfb72b50af4d24e9fdd
github_commit Patch Available

commit 57aec90ac57b (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12 (contains commit 57aec90ac57b)

https://github.com/xmldom/xmldom/commit/57aec90ac57b4408ae7c5d1746bf2a693b5ed90e
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

DocType `name` Injection Bypasses requireWellFormed · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-27p8-2357-5qqv

Vendor Advisories for CVE-2026-83608(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 / 51× 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 21:44 UTCEG score recompute
  2. 2026-09-18 21:44 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 09:14 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 07:53 UTCVendor advisory
  9. 2026-09-16 19:23 UTCEG score recompute
  10. 2026-09-16 19:23 UTCVendor advisory
  11. 2026-09-16 14:09 UTCEPSS rescore
  12. 2026-09-16 06:53 UTCEG score recompute
  13. 2026-09-16 06:53 UTCVendor advisory
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 18:23 UTCVendor advisory
  16. 2026-09-15 05:36 UTCEG score recompute
  17. 2026-09-15 05:36 UTCVendor advisory
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 16:11 UTCVendor advisory
  21. 2026-09-14 03:41 UTCEG score recompute
  22. 2026-09-14 03:41 UTCVendor advisory
  23. 2026-09-13 15:11 UTCVendor advisory
  24. 2026-09-13 02:39 UTCEG score recompute
  25. 2026-09-13 02:39 UTCVendor advisory
Show 26 more
  1. 2026-09-12 14:09 UTCVendor advisory
  2. 2026-09-12 01:39 UTCEG score recompute
  3. 2026-09-12 01:39 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 13:08 UTCEG score recompute
  7. 2026-09-10 12:08 UTCEG score recompute
  8. 2026-09-09 09:42 UTCEG score recompute
  9. 2026-09-09 09:42 UTCVendor advisory
  10. 2026-09-08 22:01 UTCEPSS rescore
  11. 2026-09-08 06:39 UTCVendor advisory
  12. 2026-09-07 18:09 UTCEG score recompute
  13. 2026-09-07 18:09 UTCVendor advisory
  14. 2026-09-06 17:07 UTCEG score recompute
  15. 2026-09-06 13:48 UTCEPSS rescore
  16. 2026-09-05 16:05 UTCEG score recompute
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-04 15:03 UTCEG score recompute
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-04 02:28 UTCEG score recompute
  21. 2026-09-04 02:04 UTCEG score recompute
  22. 2026-09-02 16:46 UTCEG score recompute
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 15:40 UTCEG score recompute
  25. 2026-09-01 14:34 UTCEG score recompute
  26. 2026-09-01 14:33 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83608?
CVE-2026-83608 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, the DOCUMENTTYPENODE branch in lib/dom.js validates publicId, systemId, and internalSubset under…
When was CVE-2026-83608 disclosed?
CVE-2026-83608 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-83608 actively exploited?
CVE-2026-83608 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-83608?
CVE-2026-83608 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-83608?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83608, 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-83608

Explore →

Is Your Infrastructure Affected by CVE-2026-83608?

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

Start Free Scan →Browse All CVEs