Vulnerability in dompurify (CVE-2026-65913)
Summary
Vulnerability in dompurify (CVE-2026-65913). Risk of unauthorized operations or information disclosure. Exploitable via USE_PROFILES. Mitigation: upgrade to 3.3.2 or later.
Original description
The description as published by the source.
Summary
When USE_PROFILES is enabled, DOMPurify rebuilds ALLOWED_ATTR as a plain array before populating it with the requested allowlists. Because the sanitizer still looks up attributes via ALLOWED_ATTR[lcName], any Array.prototype property that is polluted also counts as an allowlisted attribute. An attacker who can set Array.prototype.onclick = true (or a runtime already subject to prototype pollution) can thus force DOMPurify to keep event handlers such as onclick even when they are normally forbidden. The provided PoC sanitizes `` with USE_PROFILES and adds the sanitized output to the DOM; the polluted prototype allows the event handler to survive and execute, turning what should be a blocklist into a silent XSS vector.
Impact
Prototype pollution makes DOMPurify accept dangerous event handler attributes, which bypasses the sanitizer and results in DOM-based XSS once the sanitized markup is rendered.
Credits
Identified by Cantina’s Apex (https://www.cantina.security).
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-65913 has been found in dompurify.
Attackers can target a specific entry point like USE_PROFILES over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade dompurify to 3.3.2 or later.
If unsure, ask your IT team or search "dompurify CVE-2026-65913" on the vendor's site.
CVE-2026-65913 (dompurify) — CWE-1321 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: USE_PROFILES / ALLOWED_ATTR / Array.prototype / onclick
Patched: 3.3.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in dompurify. Attackers reach the vulnerable code path via USE_PROFILES without authentication.
Check the vendor advisory for the affected versions of dompurify. Attack surface: USE_PROFILES / ALLOWED_ATTR / Array.prototype / onclick.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dompurify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dompurify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dompurifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dompurify to 3.3.2ステージング環境で 3.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-65913 node-dompurify
References
- advisory disclosure@vulncheck.com
- advisory disclosure@vulncheck.com
- package github.com
- web github.com
- web github.com