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.
{
"cna_assigner": "VulnCheck",
"cwe_ids": [
"CWE-693"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/65xxx/CVE-2026-65899.json"
}{
"extracted_events": [
{
"cpe": "cpe:2.3:a:cure53:dompurify:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.0.0"
},
{
"fixed": "3.4.9"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "825e617753ac1169306a542d3174a77f717a0cf6"
}
],
"source": "REFERENCES_COMMIT"
}
]
}