CVE-2026-65899

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 4.0

5.1CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

CVSS 3.1

6.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

0.4% chance of exploitation in the next 30 days; higher than 35% of CVEs (scores of 2026-10-25)

CWE

CWE-693

Published

2026-07-23

Modified

2026-10-24

Record from

the NVD, synced 2026-10-24

Affected

• cure53:dompurify

Packages (OSV)

References

• https://github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6
• https://github.com/cure53/DOMPurify/security/advisories/GHSA-vxr8-fq34-vvx9
• https://www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contamination

Check your stackJSON