CVE-2026-65899

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.4% (36th 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

Also known asEUVD-2026-48268 (ENISA EUVD) · GHSA-vxr8-fq34-vvx9 (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a TrustedHTML object created by the old (potentially unsafe) policy rather than a clean default, which can lead to script execution at a Trusted Types sink. Passing TRUSTED_TYPES_POLICY: null on the later call also does not clear the retained policy.

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.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

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

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

DOMPurify before 3.4.9 Trusted Types Policy State Contamination | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contamination
GitHub commit

commit 825e617753ac (cure53/DOMPurify)

Fix landed in cure53/DOMPurify commit 825e617753ac — awaiting tagged release

https://github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6
GitHub advisoryMentions a patch (unverified)

Trusted Types policy survives `clearConfig()` and can poison later `RETURN_TRUSTED_TYPE` output · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-vxr8-fq34-vvx9

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana13-1-main-13.1.3-0.1.3.hum12026-08-22redhat
redhatgrafana12-4-main-12.4.8-0.1.2.hum12026-08-22redhat
npmdompurify @ 3.4.9 (fixes < 3.4.9)—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 up to 3.4.9: fixed in 3.4.9
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 190 rows 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 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-65899?
CVE-2026-65899 is a medium-severity vulnerability; its CVE record was published on July 23, 2026. DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a…
When was CVE-2026-65899 made public?
CVE-2026-65899 was made public on June 10, 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-65899 actively exploited?
CVE-2026-65899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65899?
CVE-2026-65899 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-65899?
A fix for CVE-2026-65899 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65899 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-65899

Explore →

Is Your Infrastructure Affected by CVE-2026-65899?

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