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.
CVE-2026-65904
This medium-severity CVE scores 4.7 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.7
- EG Score
- 4.7(low)
- EG Risk
- 26(Track)EG Risk 26/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity47% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 5.0%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 24, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026DOMPurify before 3.4.4 Cross-Site Scripting via IN_PLACE mode | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-cross-site-scripting-via-in-place-modeDOMPurify IN_PLACE mode fails to sanitize cross-window DOM elements, allowing XSS bypass · Advisory · cure53/DOMPurify · GitHub
https://github.com/cure53/DOMPurify/security/advisories/GHSA-4w3q-35jp-p934Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 13:25 UTCEG score recompute
- 2026-07-23 13:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-754
Frequently asked(5)
What is CVE-2026-65904?
When was CVE-2026-65904 disclosed?
Is CVE-2026-65904 actively exploited?
What is the CVSS score of CVE-2026-65904?
How do I remediate CVE-2026-65904?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65904
Is Your Infrastructure Affected by CVE-2026-65904?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.