CVE-2026-65902: medium-severity vulnerability in cure53 DOMPurify
DOMPurify before 3.4.7 Hook Mutation Pollution via allowedTags
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.3epss 0.4%
DOMPurify before 3.4.7 passes direct references to the module-level DEFAULT_ALLOWED_TAGS and DEFAULT_ALLOWED_ATTR sets to the uponSanitizeElement and uponSanitizeAttribute hooks via data.allowedTags / data.allowedAttributes when sanitize is called without an explicit cfg.ALLOWED_TAGS / cfg.ALLOWED_ATTR array. A hook that mutates these fields permanently widens the default allow-lists for the lifetime of the DOMPurify instance, so all subsequent default-config sanitize calls inherit the widened defaults and attacker payloads using the poisoned tag/attribute name survive sanitization. removeAllHooks(), clearConfig(), and passing a fresh cfg do not recover the state; only constructing a new DOMPurify instance does.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N
Affected products
cure53 · DOMPurifyRelated CVEs — cure53 DOMPurify
In the same product, most dangerous first.
CVE-2024-48910CRITICALDOMPurify vulnerable to tampering by prototype polutionEPSS 1.2%CVE-2024-47875CRITICALDOMPurify nesting-based mXSSEPSS 1.1%CVE-2024-45801HIGHTampering by prototype polution in DOMPurifyEPSS 0.9%CVE-2026-65899MEDIUMDOMPurify before 3.4.9 Trusted Types Policy State ContaminationEPSS 0.4%CVE-2026-47423HIGHDOMPurify XSS via `selectedcontent` re-cloneEPSS 0.4%CVE-2026-49978MEDIUMDOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.contentEPSS 0.4%