Back to CVE records
Medium 6.1Published Jul 23, 2026

CVE-2026-65899DOMPurify before 3.4.9 Trusted Types Policy State Contamination

Updated under an hour ago ()

Does this affect you?

It affects cure53 DOMPurify. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.1 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-693
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
VulnCheck
NVD analysis
Analyzed
Record last updated
Oct 8, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
cure53 DOMPurify
cure53:dompurify (from the name)
before 3.4.9; 3.4.9 not affected
CNA record
cure53 dompurify
cure53:dompurify
from 3.0.0 before 3.4.9
NVD

References

  • vendor-advisory
  • patch
  • third-party-advisory

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.