CVE-2026-83611

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-69225 (ENISA EUVD) · GHSA-6h8r-xr42-gp59 (GitHub Security Advisories)Source: ENISA EUVD

6.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 6.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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, DOMParser.parseFromString() can silently accept an end tag such as , close the element, and discard the trailing content. On 0.9.x, the lib/sax.js end-tag validator inherits the multiline flag from reg(), allowing the first line to satisfy the anchored XML ETag production; older lines have no equivalent residue validation. This parser differential can bypass a parse-before-trust well-formedness gate, although it does not inject the discarded content; onError on 0.9.x and errorHandler on 0.8.x are the relevant reporting interfaces. 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.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
62
EG Risk 62/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (7)

Auto-updated Sep 1, 2026
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 7b2ec67e1750 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12 (contains commit 7b2ec67e1750)

https://github.com/xmldom/xmldom/commit/7b2ec67e1750daadd0bb06c92e875e726544a362
GitHub commit Patch Available

commit 4430189660b0 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit 4430189660b0)

https://github.com/xmldom/xmldom/commit/4430189660b0d380ee9c9ee7550a1358688e8828
GitHub pull request 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 pull request 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 advisoryMentions a patch (unverified)

Parser silently accepts a not-well-formed end tag whose name is followed by a line break and trailing content · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-6h8r-xr42-gp59

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmxmldom—ghsa
npm@xmldom/xmldom @ 0.8.15 (fixes >= 0.7.0, <= 0.8.14)—ghsa
npm@xmldom/xmldom @ 0.9.12 (fixes >= 0.9.0, <= 0.9.11)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
xmldom—
  • every version through 0.6.0: no fix on record
—
@xmldom/xmldom—
  • 0.7.0 up to 0.8.15: fixed in 0.8.15
  • 0.9.0 up to 0.9.12: fixed in 0.9.12
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-xmldom0.8.6-1 ... 0.9.9-1 (10 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-xmldom0.9.10-1 ... 0.9.9-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-xmldom0.9.10-1 ... 0.9.9-1 (7 versions)
  • every version up to 0.9.12-1: fixed in 0.9.12-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 127 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  2. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-6h8r-xr42-gp59 · GitHub severity MODERATE
  3. 2026-11-01 07:38 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  6. 2026-10-30 00:55 UTCOSV refresh
  7. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  8. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  12. 2026-10-25 13:56 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-22 13:41 UTCEG score recompute
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-10-18 03:07 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
Show 75 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  3. 2026-10-12 14:54 UTCEG score recompute
  4. 2026-10-11 19:19 UTCEG score recompute
  5. 2026-10-11 16:35 UTCEG score recompute
  6. 2026-10-11 13:53 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  9. 2026-10-10 05:04 UTCEG score recompute
  10. 2026-10-10 05:04 UTCVendor advisory
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-09 02:07 UTCEG score recompute
  13. 2026-10-09 02:07 UTCVendor advisory
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-10-07 09:24 UTCEG score recompute
  17. 2026-10-07 09:24 UTCVendor advisory
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-06 07:21 UTCEG score recompute
  20. 2026-10-06 07:21 UTCVendor advisory
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  22. 2026-10-05 04:34 UTCEG score recompute
  23. 2026-10-05 04:34 UTCVendor advisory
  24. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  25. 2026-10-04 02:33 UTCEG score recompute
  26. 2026-10-04 02:33 UTCVendor advisory
  27. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  28. 2026-10-03 00:31 UTCEG score recompute
  29. 2026-10-03 00:31 UTCVendor advisory
  30. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  31. 2026-10-01 22:30 UTCEG score recompute
  32. 2026-10-01 22:30 UTCVendor advisory
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  34. 2026-09-30 19:34 UTCEG score recompute
  35. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  36. 2026-09-29 14:02 UTCEG score recompute
  37. 2026-09-29 14:02 UTCVendor advisory
  38. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  39. 2026-09-28 11:05 UTCEG score recompute
  40. 2026-09-28 11:05 UTCVendor advisory
  41. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-09-27 09:03 UTCEG score recompute
  43. 2026-09-27 09:03 UTCVendor advisory
  44. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  45. 2026-09-26 07:01 UTCEG score recompute
  46. 2026-09-26 07:01 UTCVendor advisory
  47. 2026-09-25 04:26 UTCEG score recompute
  48. 2026-09-25 04:26 UTCVendor advisory
  49. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  50. 2026-09-24 02:25 UTCEG score recompute
  51. 2026-09-24 02:25 UTCVendor advisory
  52. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-09-23 00:23 UTCEG score recompute
  54. 2026-09-23 00:23 UTCVendor advisory
  55. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  56. 2026-09-21 22:22 UTCEG score recompute
  57. 2026-09-21 22:22 UTCVendor advisory
  58. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  59. 2026-09-20 20:19 UTCEG score recompute
  60. 2026-09-20 20:19 UTCVendor advisory
  61. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  62. 2026-09-19 18:18 UTCEG score recompute
  63. 2026-09-19 18:18 UTCVendor advisory
  64. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  65. 2026-09-18 16:17 UTCEG score recompute
  66. 2026-09-18 16:17 UTCVendor advisory
  67. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  68. 2026-09-17 13:49 UTCEG score recompute
  69. 2026-09-17 13:49 UTCVendor advisory
  70. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  71. 2026-09-16 11:47 UTCEG score recompute
  72. 2026-09-16 11:47 UTCVendor advisory
  73. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  74. 2026-09-15 09:46 UTCEG score recompute
  75. 2026-09-15 09:46 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-83611?
CVE-2026-83611 is a medium-severity vulnerability; its CVE record was 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, DOMParser.parseFromString() can silently accept an end tag such as </a\njunk>, close the element,…
When was the CVE record for CVE-2026-83611 published?
The CVE record for CVE-2026-83611 was published on September 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-83611 actively exploited?
CVE-2026-83611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-83611?
CVE-2026-83611 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-83611?
A fix for CVE-2026-83611 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-83611 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-83611?

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