Disclosure summary
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.
Source-reported weakness categories
CWE-693
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
NIST National Vulnerability Database · NVD-CVE-2026-65899
Open original source · Updated Oct 08, 2026
Only CPE matches marked vulnerable=true are indexed. AND/OR platform conditions must be checked in the original NVD record.
| Vendor | Product / association | Version / bounds |
|---|---|---|
| cure53 | dompurify | * {"versionStartIncluding":"3.0.0","versionEndExcluding":"3.4.9"} |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Patch
- github.com — Exploit, Third Party Advisory
- www.vulncheck.com — Third Party Advisory
PUBLISHED 2026-07-23T10:18:04-04:00
MODIFIED 2026-10-08T12:17:29-04:00
INGESTED 2026-10-10T20:50:36-04:00