CVE-2026-116803: cure53 DOMPurify · Cross-site Scripting
Affects cure53 DOMPurifySource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 3.4.17 when convenient.
Data as of 26 Oct 2026, 23:42 UTC
- Patch
- Available – fixed in 3.4.17
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade cure53 DOMPurify to 3.4.17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| cure53DOMPurify | Affected
| Fixed in
|
npmDOMPurifypkg:npm/DOMPurifyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
DOMPurify before 3.4.17 contains a cross-site scripting vulnerability that allows attackers to keep event handlers armed when an IN_PLACE hook removes a parent or sibling node. Attacker markup in detached subtrees is never walked or neutralized, so handlers like img onerror fire after sanitize() returns, causing DOM XSS.