Vulnerability in dompurify (CVE-2026-49459)
Summary
Vulnerability in dompurify (CVE-2026-49459). Risk of unauthorized operations or information disclosure. Exploitable via _forceRemove. Mitigation: upgrade to 3.4.6 or later.
Original description
The description as published by the source.
DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Prior to 3.4.6, DOMPurify.sanitize(root, { IN_PLACE: true }) could preserve event-handler attributes on an attacker-controlled root when a descendant name clobbered properties checked by _isClobbered, because _forceRemove no-opped on the parent-less root and _sanitizeAttributes returned early. This issue is fixed in version 3.4.6.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-49459 has been found in dompurify.
Attackers can target a specific entry point like _forceRemove 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.4.6 or later.
If unsure, ask your IT team or search "dompurify CVE-2026-49459" on the vendor's site.
CVE-2026-49459 (dompurify) — CWE-1321 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: _forceRemove / root / onmouseover / onfocus
Patched: 3.4.6 — 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 _forceRemove without authentication.
Check the vendor advisory for the affected versions of dompurify. Attack surface: _forceRemove / root / onmouseover / onfocus.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.4.6.
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.4.6ステージング環境で 3.4.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- Debian DEBIAN-CVE-2026-49459 node-dompurify
- Ubuntu UBUNTU-CVE-2026-49459 dompurify.js
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com