DOMPurify before 3.3.2 contains a mutation-XSS vulnerability when sanitized HTML is reinserted into special parsing contexts using innerHTML with wrappers like script, xmp, iframe, noembed, noframes, or noscript. Attackers can craft payloads with closing sequences that break out of the wrapper context during reparsing, reactivating dangerous markup with event handlers to execute JavaScript.
CVE-2026-65914
MEDIUMPre-NVD 5.35.3—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity53% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jul 23, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
DOMPurify before 3.3.2 Mutation XSS via Re-Contextualization | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-mutation-xss-via-re-contextualizationgithub Patch Available🟡 PoC Available
DOMPurify mXSS via Re-Contextualization · Advisory · cure53/DOMPurify · GitHub
https://github.com/cure53/DOMPurify/security/advisories/GHSA-h8r8-wccr-v5f2Vendor Advisories for CVE-2026-65914(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dompurify | — | 3.3.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-27 01:31 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 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)
Frequently asked(5)
What is CVE-2026-65914?
CVE-2026-65914 is a medium vulnerability published on July 23, 2026. DOMPurify before 3.3.2 contains a mutation-XSS vulnerability when sanitized HTML is reinserted into special parsing contexts using innerHTML with wrappers like script, xmp, iframe, noembed, noframes, or noscript. Attackers can craft payloads with closing sequences that break out of the wrapper…
When was CVE-2026-65914 disclosed?
CVE-2026-65914 was first published in the National Vulnerability Database on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65914 actively exploited?
CVE-2026-65914 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.2% of all scored CVEs.
What is the CVSS score of CVE-2026-65914?
CVE-2026-65914 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-65914?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65914, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65914
Is Your Infrastructure Affected by CVE-2026-65914?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.