CVE-2026-83619

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 77% 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 week
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: None knownExposed: 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. 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.7(medium)
EG Risk
54(Track)
EG Risk 54/100SSVC: Track

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 8, 2026

Advisory Details (4)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. 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_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 Patch Available🟡 PoC Available

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

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.8.6-1 ... 0.9.9-1 (9 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.5-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.5-1
npm(1)
PackageVulnerable rangeFixed inDependents
@xmldom/xmldom0.8.15

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 55× 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-19 08:16 UTCVendor advisory
  2. 2026-09-18 21:25 UTCEG score recompute
  3. 2026-09-18 21:25 UTCVendor advisory
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 09:27 UTCVendor advisory
  6. 2026-09-17 22:37 UTCEG score recompute
  7. 2026-09-17 22:37 UTCVendor advisory
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 11:45 UTCVendor advisory
  10. 2026-09-17 00:55 UTCEG score recompute
  11. 2026-09-17 00:55 UTCVendor advisory
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 14:05 UTCEG score recompute
  14. 2026-09-16 14:05 UTCVendor advisory
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-16 03:15 UTCVendor advisory
  17. 2026-09-15 16:25 UTCVendor advisory
  18. 2026-09-15 05:36 UTCEG score recompute
  19. 2026-09-15 05:36 UTCVendor advisory
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 18:30 UTCVendor advisory
  23. 2026-09-14 07:10 UTCVendor advisory
  24. 2026-09-13 20:21 UTCEG score recompute
  25. 2026-09-13 20:21 UTCVendor advisory
Show 30 more
  1. 2026-09-13 09:31 UTCVendor advisory
  2. 2026-09-12 22:41 UTCEG score recompute
  3. 2026-09-12 22:41 UTCVendor advisory
  4. 2026-09-12 11:51 UTCVendor advisory
  5. 2026-09-12 01:01 UTCEG score recompute
  6. 2026-09-12 01:01 UTCVendor advisory
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:11 UTCEG score recompute
  10. 2026-09-10 16:31 UTCEG score recompute
  11. 2026-09-09 18:51 UTCVendor advisory
  12. 2026-09-09 08:01 UTCEG score recompute
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-08 03:26 UTCVendor advisory
  15. 2026-09-07 16:36 UTCEG score recompute
  16. 2026-09-07 16:36 UTCVendor advisory
  17. 2026-09-06 18:56 UTCEG score recompute
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-05 21:14 UTCEG score recompute
  20. 2026-09-05 15:31 UTCEPSS rescore
  21. 2026-09-04 23:27 UTCEG score recompute
  22. 2026-09-04 12:31 UTCEG score recompute
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-02 17:11 UTCEG score recompute
  25. 2026-09-02 14:12 UTCEPSS rescore
  26. 2026-09-01 19:30 UTCEG score recompute
  27. 2026-09-01 18:25 UTCEG score recompute
  28. 2026-09-01 15:38 UTCEG score recompute
  29. 2026-09-01 14:55 UTCEG score recompute
  30. 2026-09-01 14:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-83619?
CVE-2026-83619 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. 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 CVE-2026-83619 disclosed?
CVE-2026-83619 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-83619 actively exploited?
CVE-2026-83619 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 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-83619?
CVE-2026-83619 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-83619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-83619, 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-83619

Explore →

Is Your Infrastructure Affected by CVE-2026-83619?

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