CVE-2026-65902
DOMPurify before 3.4.7 (affected versions <= 3.4.5) passes direct …
DOMPurify before 3.4.7 (affected versions <= 3.4.5) 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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/cure53/DOMPurify/commit/7996f1dc78eb8b7922388aed75d94a9f8fad9a36
- github.com/cure53/DOMPurify/security/advisories/GHSA-76mc-f452-cxcm
- www.vulncheck.com/advisories/dompurify-before-hook-mutation-pollution-via-allowedtags
- github.com/advisories/GHSA-76mc-f452-cxcm
- nvd.nist.gov/vuln/detail/CVE-2026-65902
- cve.org/CVERecord?id=CVE-2026-65902
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.