CVE-2026-83619

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.5% (44th 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 — 5 sources updated this week

Also known asEUVD-2026-69248 (ENISA EUVD) · GHSA-x4fp-j954-r2f4 (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.5%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. From 0.7.0 until 0.8.15, the release-0.8.x parser in lib/sax.js trims captured end-tag names with the unanchored global expression /[ \t\n\r]+$/g. For an end tag containing a long whitespace run followed by a non-whitespace character, the expression retries from each possible starting position and backtracks quadratically before failing its end anchor. DOMParser.parseFromString() reaches the path under default options, allowing a small unauthenticated XML input to stall the Node.js event loop; the 0.9.x and unscoped npm lines do not contain this expression. This issue is fixed in @xmldom/xmldom version 0.8.15.

CVSS v3
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.5% × 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.5%
EPSS %ILE
44th
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 · CVSS v3.0 or v3.1
EG Likelihood
0.5% 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 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 (4)

Auto-updated Sep 1, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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 3abb0934f5a8 (xmldom/xmldom)

Patch available: xmldom/xmldom 0.8.15 (contains commit 3abb0934f5a8)

https://github.com/xmldom/xmldom/commit/3abb0934f5a8a84d83a1f9cde0f2bd04c08b2a09
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 advisoryMentions a patch (unverified)

End-tag Whitespace-Trim Regex ReDoS (CWE-1333) — quadratic backtracking in the 0.8.x end-tag parser · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-x4fp-j954-r2f4

Vendor Advisories for CVE-2026-83619(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
npm@xmldom/xmldom @ 0.8.15 (fixes >= 0.7.0, <= 0.8.14)—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

(4 across 4 ecosystems)
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-xmldom—
  • every version up to 0.9.5-1: fixed in 0.9.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-xmldom—
  • every version up to 0.9.5-1: fixed in 0.9.5-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@xmldom/xmldom—
  • 0.7.0 up to 0.8.15: fixed in 0.8.15
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 63× 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 176 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 76 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-83619?
CVE-2026-83619 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. From 0.7.0 until 0.8.15, the release-0.8.x parser in lib/sax.js trims captured end-tag names with the unanchored global expression /[ \t\n\r]+$/g. For an end tag containing a long whitespace…
When was the CVE record for CVE-2026-83619 published?
The CVE record for CVE-2026-83619 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-83619 actively exploited?
CVE-2026-83619 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-83619?
CVE-2026-83619 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-83619?
A fix for CVE-2026-83619 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-83619 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-83619

Explore →

Is Your Infrastructure Affected by CVE-2026-83619?

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

Book a Demo →Browse All CVEs