CVE-2026-83610

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% 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
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: 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, Document.createEntityReference(name) accepts an invalid name and the ENTITY_REFERENCE_NODE serializer emits the resulting nodeName directly in &name; form. Directly serializing the node or fragment with XMLSerializer.serializeToString() and requireWellFormed: true can therefore break the entity-reference boundary and produce attacker-controlled XML markup when reparsed. The parser does not ordinarily create these nodes, and element-child insertion is rejected, so exploitation requires an application to create and directly serialize an EntityReference. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
59(Attend)
EG Risk 59/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
Severity63% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
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.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 6c3fb5ffeafe (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit 6c3fb5ffeafe)

https://github.com/xmldom/xmldom/commit/6c3fb5ffeafe7901ec928ce9010988dd716c94a0
github_commit Patch Available

commit 4664386e4f4d (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12 (contains commit 4664386e4f4d)

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

XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-6gmq-8vp8-gcm6

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-83610?
CVE-2026-83610 is a medium 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, Document.createEntityReference(name) accepts an invalid name and the ENTITYREFERENCENODE serializer…
When was CVE-2026-83610 disclosed?
CVE-2026-83610 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-83610 actively exploited?
CVE-2026-83610 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 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-83610?
CVE-2026-83610 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-83610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83610, 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-83610

Explore →

Is Your Infrastructure Affected by CVE-2026-83610?

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

Start Free Scan →Browse All CVEs