DOMPurify from 3.4.4 before 3.4.17 SAFE_FOR_TEMPLATES Bypass via Shadow Root Content
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.4.17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.17.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.18% · 7th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 47/100
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
DOMPurify, a JavaScript library used to sanitize HTML in web applications, is affected by a flaw that can let malicious template expressions survive sanitization when certain output modes are used. This could allow attackers to run cross-site scripting attacks if the sanitized output is later processed by a template engine.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
DOMPurify from 3.4.4 before 3.4.17 contains a SAFE_FOR_TEMPLATES bypass that lets attackers preserve template expressions in attached shadow roots when using RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE modes. Attackers can split expressions across text nodes separated by disallowed elements, which merge after removal and are evaluated by downstream template engines for cross-site scripting.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20dompurify: 95.8M downloads a week
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
- Would score about 62 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 3.4.17.
Timeline
- CVE published
- First seen by cve.now7 days
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- cure53 DOMPurify
From 3.4.4 · fixed in 3.4.17
- dompurifynpm
From 3.4.4 · fixed in 3.4.17
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116804
Is CVE-2026-116804 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116804?
DOMPurify: from 3.4.4 before 3.4.17. dompurify (npm): from 3.4.4 before 3.4.17.Source: cve.now feed data
How do I fix CVE-2026-116804?
Upgrade to a fixed version: 3.4.17.Source: cve.now feed data