CVE-2026-65901

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (21st 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 — 4 sources updated this weekElevated

Also known asEUVD-2026-48270 (ENISA EUVD) · GHSA-x4vx-rjvf-j5p4 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

DOMPurify through 3.4.6 contains a cross-site scripting vulnerability in IN_PLACE mode that trusts attacker-controlled nodeName on live non-form nodes. Attackers can supply hostile live DOM objects with real script children whose observable nodeName is clobbered to appear as allowed elements, causing scripts to execute when the sanitized tree is inserted into a live document.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.3%
EPSS %ILE
21st
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

July 23, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Jul 23, 2026
Patch available. Sources: github.
Web page

DOMPurify 3.4.6 Cross-Site Scripting via IN_PLACE nodeName | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-cross-site-scripting-via-in-place-nodename
GitHub advisoryMentions a patch (unverified)

`IN_PLACE` mode trusts attacker-controlled `nodeName` on live non-form nodes, allowing script retention and XSS via attacker-supplied DOM objects · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-x4vx-rjvf-j5p4

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana12-4-main-12.4.8-0.1.2.hum12026-08-22redhat
redhatgrafana13-1-main-13.1.3-0.1.3.hum12026-08-22redhat
npmdompurify—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-dompurify2.4.1+dfsg+~2.4.0-1 ... 3.4.5+dfsg-1 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (8 versions)
  • every version up to 3.4.12+dfsg-1: fixed in 3.4.12+dfsg-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
dompurify—
  • every version through 3.4.6: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-65901?
CVE-2026-65901 is a medium-severity vulnerability; its CVE record was published on July 23, 2026. DOMPurify through 3.4.6 contains a cross-site scripting vulnerability in IN_PLACE mode that trusts attacker-controlled nodeName on live non-form nodes. Attackers can supply hostile live DOM objects with real script children whose observable nodeName is clobbered to appear as allowed elements,…
When was CVE-2026-65901 made public?
CVE-2026-65901 was made public on May 27, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 23, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-65901 actively exploited?
CVE-2026-65901 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65901?
CVE-2026-65901 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65901?
A fix for CVE-2026-65901 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65901 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-65901

Explore →

Is Your Infrastructure Affected by CVE-2026-65901?

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