CVE-2026-41239 | DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode

DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Starting in version 1.0.10 and prior to version 3.4.0, `SAFE_FOR_TEMPLATES` strips `{{...}}` expressions from untrusted HTML. This works in string mode but not with `RETURN_DOM` or `RETURN_DOM_FRAGMENT`, allowing XSS via template-evaluating frameworks like Vue 2. Version 3.4.0 patches the issue.

Published: 2026-04-23 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41239 is rated Low Risk (31.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.22%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41239

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.05% 0.22% +0.16%
2 2026-04-29 0.05% 0.05% +0.01%
3 2026-04-24 — 0.05% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41239

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 5.2 [email protected]

Weakness enumeration for CVE-2026-41239

GitHub Security Advisory for CVE-2026-41239

GHSA-crv5-9vww-q3g8 · Severity: medium · Ecosystem: npm — DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode

OS Trackers for CVE-2026-41239

vendor priority summary link
debian not yet assigned CVE-2026-41239 not yet assigned priority: Debian including 1 source packages (node-dompurify), 4 status rows across 4 suites (bookworm, forky, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-41239
redhat medium — https://access.redhat.com/security/cve/CVE-2026-41239
ubuntu medium CVE-2026-41239 medium priority: Ubuntu including 1 source packages (node-dompurify), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): needs-triage 5. https://ubuntu.com/security/CVE-2026-41239

Affected software / configurations for CVE-2026-41239

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-41239

cvelogic Threat Intelligence