DOMPurify before 3.4.13 contains a cross-site scripting vulnerability in IN_PLACE sanitization where element-removal hooks fail to neutralize detached subtrees. Attackers can supply HTML with event handlers on descendant elements that execute after sanitization completes, even though the returned root appears clean.
CVE-2026-75838
This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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).
- 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
- 5.1
- EG Score
- 5.1(medium)
- EG Risk
- 39(Track)EG Risk 39/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 computedSeverity51% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 18, 2026DOMPurify before 3.4.13 Cross-Site Scripting via IN_PLACE hook | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dompurify-before-cross-site-scripting-via-in-place-hookIN_PLACE hook removal leaves a detached subtree executable, causing XSS · Advisory · cure53/DOMPurify · GitHub
https://github.com/cure53/DOMPurify/security/advisories/GHSA-55q2-fjhq-7xh7Vendor Advisories for CVE-2026-75838(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 14× 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-08-20 22:56 UTCEPSS rescore
- 2026-08-20 10:53 UTCEG score recompute
- 2026-08-20 10:53 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 12:50 UTCEG score recompute
- 2026-08-19 12:50 UTCGHSA enrichment
- 2026-08-18 14:47 UTCEG score recompute
- 2026-08-18 14:46 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEG score recompute
- 2026-08-18 13:48 UTCGHSA enrichment
- 2026-08-18 12:34 UTCEG score recompute
- 2026-08-18 12:34 UTCGHSA enrichment
- 2026-08-18 11:29 UTCEG score recompute
- 2026-08-18 11:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75838?
When was CVE-2026-75838 disclosed?
Is CVE-2026-75838 actively exploited?
What is the CVSS score of CVE-2026-75838?
How do I remediate CVE-2026-75838?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75838
Is Your Infrastructure Affected by CVE-2026-75838?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.