CVE-2026-83614

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th 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

Also known asEUVD-2026-69234 (ENISA EUVD) · GHSA-93r5-fhx6-vmg9 (GitHub Security Advisories)Source: ENISA EUVD

8.7EG
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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.7Exploit: None knownExposed 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 versions 0.3.0 through 0.6.0, two independent quadratic paths can cause denial of service. In lib/sax.js, parseElementStartPart repeatedly rescans a malformed tag name to the next > during single-character recovery; in lib/dom.js, normalize() repeatedly removes and appends adjacent text nodes, causing quadratic reindexing and string rebuilding. The first path is reachable through default DOMParser.parseFromString() processing, while the second is also reachable through a direct normalize() call on a programmatically constructed DOM, and endDocument invokes that normalization after parsing. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.

CVSS
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/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)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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
48th
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 (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 none (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 f40ccb861eee (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit f40ccb861eee)

https://github.com/xmldom/xmldom/commit/f40ccb861eee0acbf5ee4feb9a34932e87b329c9
GitHub commit Patch Available

commit 0748720b6205 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.9.12 (contains commit 0748720b6205)

https://github.com/xmldom/xmldom/commit/0748720b620555f8c222782dcab575cf0cf403b4
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)

Quadratic-time parsing via the malformed-input recovery path (CWE-407) — `parseElementStartPart` re-scan and `normalize()` adjacent-text merge · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-93r5-fhx6-vmg9

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
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—
  • 0.3.0 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(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 189 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-83614?
CVE-2026-83614 is a high-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 versions 0.3.0 through 0.6.0, two independent quadratic paths can cause denial of service. In lib/sax.js, parseElementStartPart…
When was the CVE record for CVE-2026-83614 published?
The CVE record for CVE-2026-83614 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-83614 actively exploited?
CVE-2026-83614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-83614?
CVE-2026-83614 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-83614?
A fix for CVE-2026-83614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-83614 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-83614

Explore →

Is Your Infrastructure Affected by CVE-2026-83614?

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