DOMPurify before 3.4.9 Trusted Types Policy State Contamination

Description

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.

Scores

EPSS (exploitation in 30 days)

0.41% · top 64% of all CVEs (6 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: yes · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.1.

Weakness

• CWE-693: Protection Mechanism Failure (opens in a new tab)All about CWE-693 and its CVEs

Affected products

• cure53 · DOMPurify

  • affected < 3.4.9
  • unaffected 3.4.9

Affected packages

From reviewed advisories of the GitHub Advisory Database.

• npmdompurifyGHSA-vxr8-fq34-vvx9 (opens in a new tab)

References (3)

• GitHub Security Advisory (GHSA-vxr8-fq34-vvx9) (opens in a new tab)vendor-advisory
• Patch Commit (opens in a new tab)patch
• VulnCheck Advisory: DOMPurify before 3.4.9 Trusted Types Policy State Contamination (opens in a new tab)third-party-advisory

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisory GHSA-vxr8-fq34-vvx9 (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-65899](https://trackcve.app/badge/CVE-2026-65899.svg)](https://trackcve.app/cve/CVE-2026-65899)

Record last updated 8 Oct 2026, 15:23 UTC.