CVE•Published 2026-07-23•Modified 2026-07-28•0 articles on news•4 live references•NVD data

CVE-2026-65899Cure53 · Dompurify

Vulnerability data via NVD (ingested)

CVSS v3.1

6.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS percentile

Exploit Prediction Scoring System · top 88% of all CVEs

Weaknesses (CWE)

CWE-693Protection Mechanism Failure

Description

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.

Timeline

Published 2026-07-23

Modified 2026-07-28

External references

NVD MITRE Exploit-DB VulnCheck

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

Shodan · vuln tag0 hosts

vuln:CVE-2026-65899

Hosts Shodan has explicitly fingerprinted as vulnerable.

Shodan · product

product:"Cure53 Dompurify"

All exposed Cure53 Dompurify instances — cross-reference with the CVE's affected-version range.

Shodan · banner/body mention

http.html:"Dompurify"

HTTP body or banner mentions "Dompurify" — catches deploys Shodan didn't identify as a product.

More intel sources (5)

Shodan report

vuln:CVE-2026-65899