medium6.1
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 boundar…
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| npm | dompurify | < 3.4.9 | 3.4.9 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Cure53 | Dompurify | from 3.0.0 before 3.4.9 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/advisories/GHSA-vxr8-fq34-vvx9
- https://github.com/cure53/DOMPurify/security/advisories/GHSA-vxr8-fq34-vvx9
- https://github.com/cure53/DOMPurify/commit/825e617753ac1169306a542d3174a77f717a0cf6
- https://www.vulncheck.com/advisories/dompurify-before-trusted-types-policy-state-contamination