cve.bz

CVE-2026-109344 cure53 dompurify: Cross-site Scripting

5.1 mediumEPSS 0.2%Fix available

Medium (5.1) in cure53 dompurify. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in dompurify 3.4.16.

On this page
DOMPurify from 3.4.13 before 3.4.16 contains a cross-site scripting vulnerability because IN_PLACE mode fails to neutralize subtrees detached by afterSanitizeElements or afterSanitizeAttributes hooks. Attackers can supply markup with on* handlers inside a wrapper removed by such hooks, leaving handlers armed on the live DOM to execute script in the victim origin.

Severity

CVSS 4.0

5.1 medium
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

CVSS 3.1

6.1 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-79 Improper Neutralization of Input During Web Page Generation (Cross-site Scripting)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-109344 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109344?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109344?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109344 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
cure53 DOMPurifyfrom 3.4.13 before 3.4.16

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p98j-92pf-mc4pnpmdompurify>=3.4.13 <3.4.163.4.16

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13node-dompurifyno fix listedDEBIAN-CVE-2026-109344
Debian14node-dompurify3.4.16+dfsg-1DEBIAN-CVE-2026-109344
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 1 morenode-dompurifyno fix listedUBUNTU-CVE-2026-109344

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A Moderate cross-site scripting (XSS) vulnerability was found in DOMPurify, an npm HTML-sanitization library that within Red Hat is bundled only as a dependency in components of Red Hat Hardened Images (Hummingbird). When DOMPurify sanitizes a live DOM subtree in IN_PLACE mode, elements detached by afterSanitizeElements or afterSanitizeAttributes hooks are not neutralized, because the library applies its hook-detach neutralization only at the beforeSanitizeElements and uponSanitizeElement hook sites. A remote attacker who can supply crafted markup to an application that combines IN_PLACE mode with a node-removing afterSanitize hook can hide event handlers (on* attributes) inside a wrapper element that the hook removes; those handlers remain armed on the caller's live DOM after sanitize() returns and execute attacker-controlled script in the victim's browser in the page origin. Exploitation requires user interaction, and the exact confidentiality and integrity impact depends on the hosting application's session. Red Hat rates this flaw Moderate (CVSS 6.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N), matching the severity in the CVE record; the upstream DOMPurify GitHub advisory labels the issue as low severity. Under the Hummingbird module's process, trackers are filed for bundled components regardless of impact; the delegated Hummingbird review resolved the affected components as not affected and closed the trackers as Not a Bug, recording that the vulnerable component or vulnerable code is not present in the shipped builds. No shipped Red Hat product is currently known to be affected, and no Red Hat fix is being pursued for this flaw.

Red Hat's mitigation

Applications using DOMPurify's IN_PLACE mode can mitigate this issue without changing the library by not removing nodes inside afterSanitizeElements or afterSanitizeAttributes hooks; node removals should instead be performed in beforeSanitizeElements or uponSanitizeElement hooks, where detached subtrees are neutralized. Alternatively, avoid using IN_PLACE mode for attacker-influenced content and sanitize into a detached DOM (the default behavior) instead of the live tree. Applications bundling an affected DOMPurify release can update to the upstream patched release (3.4.16 or later). The Red Hat Hardened Images (Hummingbird) components that bundle DOMPurify have been assessed as not affected, so no Red Hat product update is currently required for this issue.

ProductPackageStateAdvisory
Red Hat Hardened Imagesgrafana12.4Not affected
Red Hat Hardened Imagesgrafana13.1Not affected
Red Hat Hardened Imagesgrafana13.2Not affected
Red Hat Hardened ImagesruffNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-109344.

Attack patterns (CAPEC)

  • CAPEC-63 Cross-Site Scripting (XSS) Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-209 XSS Using MIME Type Mismatch Severity: Medium
  • CAPEC-588 DOM-Based XSS Likelihood: High · Severity: Very High
  • CAPEC-591 Reflected XSS Likelihood: High · Severity: Very High
  • CAPEC-592 Stored XSS Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON