CVE-2026-41238

DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions 3.0.1 through 3.3.3 are vulnerable to a prototype pollution-based XSS bypass. When an application uses `DOMPurify.sanitize()` with the default configuration (no `CUSTOM_ELEMENT_HANDLING` option), a prior prototype pollution gadget can inject permissive `tagNameCheck` and `attributeNameCheck` regex values into `Object.prototype`, causing DOMPurify to allow arbitrary custom elements with arbitrary attributes — including event handlers — through sanitization. Version 3.4.0 fixes the issue.

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

CVE-2026-41238 is rated Low Risk (31/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). 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-41238

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-04-24 — 0.03% —

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 4.7 [email protected]

Weakness enumeration for CVE-2026-41238

GitHub Security Advisory for CVE-2026-41238

GHSA-v9jr-rg53-9pgp · Severity: medium · Ecosystem: npm — DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback

OS Trackers for CVE-2026-41238

vendor priority summary link
debian not yet assigned CVE-2026-41238 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-41238
redhat medium — https://access.redhat.com/security/cve/CVE-2026-41238
ubuntu medium CVE-2026-41238 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-41238

Affected software / configurations for CVE-2026-41238

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-41238

cvelogic Threat Intelligence