CVE-2026-41672

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.4%, top 71% 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: 0%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, the package allows attacker-controlled comment content to be serialized into XML without validating or neutralizing comment-breaking sequences. As a result, an attacker can terminate the comment early and inject arbitrary XML nodes into the serialized output. 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
0%
EPSS %ILE
30%
KEV
Not listed

Published

May 7, 2026

Last Modified

August 28, 2026

Advisory Details (6)

Auto-updated May 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

XML node injection through unvalidated comment serialization · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-j759-j44w-7fr8
generic

Release 0.9.10 · xmldom/xmldom · GitHub

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

Release 0.8.13 · xmldom/xmldom · GitHub

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

Fix: Prevent XML injection and stack overflow DoS vulnerabilities by praveen-kv · Pull Request #987 · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/pull/987
generic

fix: prevent XML injection via unsafe comment serialization (GHSA-j75… · xmldom/xmldom@fda7cc3 · GitHub

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

fix: prevent XML injection via unsafe comment serialization (GHSA-j75… · xmldom/xmldom@b397540 · GitHub

https://github.com/xmldom/xmldom/commit/b397540889086da868c30c366ad5c220d1a750c7

Vendor Advisories for CVE-2026-41672(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(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-41672?
CVE-2026-41672 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, the package allows attacker-controlled comment content to be serialized into XML without validating or…
When was CVE-2026-41672 disclosed?
CVE-2026-41672 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-41672 actively exploited?
CVE-2026-41672 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 70.1% of all scored CVEs.
What is the CVSS score of CVE-2026-41672?
CVE-2026-41672 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-41672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41672, 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-41672

Explore →

Is Your Infrastructure Affected by CVE-2026-41672?

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

Start Free Scan →Browse All CVEs