CVE-2026-41673

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, seven recursive traversals in lib/dom.js operate without a depth limit. A sufficiently deeply nested DOM tree causes a RangeError: Maximum call stack size exceeded, crashing the application. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 7, 2026

Last Modified

August 28, 2026

Advisory Details (10)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

Release 0.8.13 · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/releases/tag/0.8.13
generic

fix: make walkDOM iterative to prevent stack overflow (GHSA-2v35-w6hq… · xmldom/xmldom@e6edcab · GitHub

https://github.com/xmldom/xmldom/commit/e6edcab6bef5bcdba0b220bb35442aa72f452b84
generic

refactor: migrate cloneNode to walkDOM · xmldom/xmldom@b062038 · GitHub

https://github.com/xmldom/xmldom/commit/b0620383abc1df067f3ce1014c43ae1bc1161eeb
generic

refactor: migrate _visitNode to walkDOM · xmldom/xmldom@8b7cfd1 · GitHub

https://github.com/xmldom/xmldom/commit/8b7cfd1491314abdc347261921d7334ff15f7112
generic

refactor: migrate textContent getter to walkDOM · xmldom/xmldom@8834218 · GitHub

https://github.com/xmldom/xmldom/commit/8834218c85ac2a4d757b9587c9028e67c2f7b6c3
generic

fix: prevent stack overflow in isEqualNode (GHSA-2v35-w6hq-6mfw) · xmldom/xmldom@4845ef1 · GitHub

https://github.com/xmldom/xmldom/commit/4845ef109221df0890825de2822fbe77afba3afe
generic

fix: prevent stack overflow in normalize (GHSA-2v35-w6hq-6mfw) · xmldom/xmldom@430357c · GitHub

https://github.com/xmldom/xmldom/commit/430357c7b6333108856e917bf2367afe5ceb6f8a
generic

refactor: introduce recursive walkDOM · xmldom/xmldom@2d6d691 · GitHub

https://github.com/xmldom/xmldom/commit/2d6d6916ed8a4c223db1f6d7560ab4544c465b0f
generic

refactor: migrate importNode to walkDOM · xmldom/xmldom@2912574 · GitHub

https://github.com/xmldom/xmldom/commit/291257493cb0eb6980eda83b162a9c4e6d7d2597
generic

refactor: migrate serializeToString to walkDOM · xmldom/xmldom@17678a2 · GitHub

https://github.com/xmldom/xmldom/commit/17678a2a73ecbd1a2da90f3d47dc23da9cef81aa

Vendor Advisories for CVE-2026-41673(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 / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17871213872026-08-27redhat
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat

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

(6 across 5 ecosystems)
npm(2)
PackageVulnerable rangeFixed inDependents
xmldom———
@xmldom/xmldom—0.9.10—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.5.0-1 ... 0.9.9-1 (14 versions)——
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.10-1 ... 0.9.9-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-xmldom0.9.6-1, 0.9.8-1, 0.9.8-2, 0.9.9-10.9.10-1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 33× 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.

Showing the most recent 100 of 186 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41673?
CVE-2026-41673 is a high vulnerability published on May 7, 2026. xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, seven recursive traversals in lib/dom.js operate without a depth limit. A sufficiently deeply nested…
When was CVE-2026-41673 disclosed?
CVE-2026-41673 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41673 actively exploited?
CVE-2026-41673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 51.1% of all scored CVEs.
What is the CVSS score of CVE-2026-41673?
CVE-2026-41673 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41673, 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-41673

Explore →

Is Your Infrastructure Affected by CVE-2026-41673?

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

Start Free Scan →Browse All CVEs