CVE-2026-65904DOMPurify through 3.3.3 fails to sanitize DOM elements passed via IN_PLACE mode when the element originates from a different window/realm (e.g., an iframe's contentDocument).
Updated under an hour ago ()
Does this affect you?
It affects cure53 dompurify. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
DOMPurify through 3.3.3 fails to sanitize DOM elements passed via IN_PLACE mode when the element originates from a different window/realm (e.g., an iframe's contentDocument). A cross-realm instanceof check in the private _isNode() function returns false for foreign-realm nodes, causing DOMPurify to stringify the element (yielding '[object HTMLDivElement]'), silently reset IN_PLACE to false, and return the unsanitized element unchanged with any XSS payloads intact.
- CVSS
- 4.7 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
- Weakness (CWE)
- CWE-754
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jul 28, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
cure53 dompurify cure53:dompurify | before 3.4.4 | NVD |
References
- https://github.com/cure53/DOMPurify/security/advisories/GHSA-4w3q-35jp-p934exploit, third-party-advisory
- https://www.vulncheck.com/advisories/dompurify-before-cross-site-scripting-via-in-place-modethird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.