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.
CVE-2026-65899
MEDIUMPre-NVD 6.16.1Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:vulncheck
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(low)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
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 computedSeverity61% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 12.0%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 23, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic
DOMPurify before 3.4.9 Trusted Types Policy State Contamination | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contaminationgithub_commit
commit 825e617753ac (cure53/DOMPurify)
Fix landed in cure53/DOMPurify commit 825e617753ac — awaiting tagged release
https://github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6github Patch Available🟡 PoC Available
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-vvx9Vendor Advisories for CVE-2026-65899(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 13:25 UTCEG score recompute
- 2026-07-23 13:24 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65899?
CVE-2026-65899 is a medium vulnerability 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 TRUSTEDTYPESPOLICY. A later caller that requests RETURNTRUSTEDTYPE output receives a TrustedHTML…
When was CVE-2026-65899 disclosed?
CVE-2026-65899 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65899 actively exploited?
CVE-2026-65899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-65899?
CVE-2026-65899 has a CVSS v3 base score of 6.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-65899?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65899, 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
Explore the affected products and dependency analysis for CVE-2026-65899
Is Your Infrastructure Affected by CVE-2026-65899?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.