CVE-2026-41674

HIGHPre-NVD 7.58.7▲
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% 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, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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 serializes DocumentType node fields (internalSubset, publicId, systemId) verbatim without any escaping or validation. When these fields are set programmatically to attacker-controlled strings, XMLSerializer.serializeToString can produce output where the DOCTYPE declaration is terminated early and arbitrary markup appears outside it. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.

CVSS v3
7.5
EG Score
8.7(medium)
EPSS
36.6%
KEV
Not listed

Published

May 7, 2026

Last Modified

June 30, 2026

Advisory Details (4)

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

XML injection through unvalidated DocumentType serialization · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-f6ww-3ggp-fr8h
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 via unsafe DocumentType serialization (GHS… · xmldom/xmldom@372008f · GitHub

https://github.com/xmldom/xmldom/commit/372008f9ae0e20fd69f761c7b79e202598267314

Vendor Advisories for CVE-2026-41674(5)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17811873422026-06-16redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17798640902026-06-03redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat
redhatopenshift4/ose-agent-installer-ui-rhel9:17792520932026-05-26redhat

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

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
xmldom———
@xmldom/xmldom—0.9.10—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 51× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41674?
CVE-2026-41674 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 serializes DocumentType node fields (internalSubset, publicId, systemId) verbatim without…
When was CVE-2026-41674 disclosed?
CVE-2026-41674 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41674 actively exploited?
CVE-2026-41674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41674?
CVE-2026-41674 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.7.
How do I remediate CVE-2026-41674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41674, 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-41674

Explore →

Is Your Infrastructure Affected by CVE-2026-41674?

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

Start Free Scan →Browse All CVEs