Skip to main content
VulnerabilityPublished

CVE-2026-116804: cure53 DOMPurify · Cross-site Scripting

Affects cure53 DOMPurifySource CVE Database V5

0

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

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
cure53DOMPurifyAffected
  • >=3.4.4 <3.4.17
Fixed in
  • 3.4.17
npmDOMPurifypkg:npm/DOMPurifyOther threatsAffected
  • >=3.4.4 <3.4.17
Fixed in
  • 3.4.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…