CVE-2026-65899

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-07-23 14:18 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-24 13:10 UTC Last updatedMost recent change to the record

Details

Published

2026-07-23 14:18 UTC

Last modified

2026-10-24 13:10 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-693

Record status

Analyzed

Affected

• cure53 Dompurify < 3.4.9

Attack profile CVSS 4.0 · 5.1

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

Active

Confidentiality

None

Integrity

None

Availability

None