CVE-2026-65899
DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/cure53/DOMPurify/security/advisories/GHSA-vxr8-fq34-vvx9
- github.com/advisories/GHSA-vxr8-fq34-vvx9
- github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6
- www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contamination
- nvd.nist.gov/vuln/detail/CVE-2026-65899
- cve.org/CVERecord?id=CVE-2026-65899
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.