DOMPurify before 3.4.9 Trusted Types Policy State Contamination
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
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-65899
DOMPurify
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "cure53",
"product": "DOMPurify",
"versions": [
{
"status": "affected",
"version": "0",
"lessThan": "3.4.9",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "3.4.9",
"versionType": "semver"
}
],
"packageURL": "pkg:npm/dompurify",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-65899
Source reference:
/cveMetadata/cveId
Publisher severity
medium
Source reference: /containers/cna/metrics
- Event
- #12798 · Revision 1
- Added to Heist Feed
- Publisher date