# CVE-2026-65913: DOMPurify before 3.3.2 Prototype Pollution via USE_PROFILES

> Attackers can bypass attribute filtering in DOMPurify's USE_PROFILES mode via prototype pollution, leading to DOM-based XSS when sanitized markup is rendered.

- **Severity:** Medium 5.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** CLEANSTART-2026-WK70378, DEBIAN-CVE-2026-65913, ECHO-94be-5b66-d788, GHSA-cj63-jhhr-wcxv, MINI-2cj9-vpvv-m9xr, MINI-4m8w-9x67-w2qm, MINI-675c-2rr7-qj44, MINI-9f23-78r5-grvx, MINI-9p3g-55qh-622c, MINI-jh33-7429-qxmc, MINI-m7mf-cjrh-qf8c, MINI-m8hg-9x28-qmmm, MINI-xc7c-7rvv-2cjg, ROOT-APP-NPM-CVE-2026-65913, ROOT-APP-NPM-GHSA-cj63-jhhr-wcxv, UBUNTU-CVE-2026-65913

## What is CVE-2026-65913?

CVE-2026-65913 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-65913?

2 open source packages ship an affected version, including dompurify. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dompurify` | npm | All versions | 3.3.2 |
| `dompurify` | npm | All versions | 3.3.2 |

Products: Cure53 Dompurify.

## How do I fix CVE-2026-65913?

Upgrade dompurify to 3.3.2 or later.

## Is CVE-2026-65913 being exploited?

There is no known exploitation of CVE-2026-65913 in the wild and no public exploit code.

## Other vulnerabilities in cure53 DOMPurify

- [CVE-2024-47875](https://insights.sbomify.com/CVE-2024-47875/): DOMPurify nesting-based mXSS (critical 10.0)
- [CVE-2024-48910](https://insights.sbomify.com/CVE-2024-48910/): DOMPurify vulnerable to tampering by prototype polution (critical 9.1)
- [CVE-2026-47423](https://insights.sbomify.com/CVE-2026-47423/): DOMPurify XSS via `selectedcontent` re-clone (high 8.2)
- [CVE-2024-45801](https://insights.sbomify.com/CVE-2024-45801/): Tampering by prototype polution in DOMPurify (high 7.3)
- [CVE-2026-49978](https://insights.sbomify.com/CVE-2026-49978/): DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside <template>.content (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65913 and fix it if it is affected.

What it is: CVE-2026-65913 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-65913 in the wild and no public exploit code.

Affected packages and fixed versions:
- dompurify (npm): affected all versions; fixed in 3.3.2
- dompurify (npm): affected all versions; fixed in 3.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65913/ (Markdown: https://insights.sbomify.com/CVE-2026-65913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65913
- OSV: https://osv.dev/vulnerability/CVE-2026-65913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65913/
Summaries are generated and may contain mistakes; the official description above is the record.