Is CVE-2026-109344 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-109344 being exploited in the wild.

How severe is CVE-2026-109344?

Medium severity, with a CVSS score of 6.1, published 12 October 2026.

Which products and versions are affected?

Cure53 DOMPurify 3.4.13 through 3.4.15.

Is there a fix for CVE-2026-109344?

Yes: fixed in 3.4.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-109344 attacked?

It is attacked over the network.

Am I affected by CVE-2026-109344?

Check whether you run Cure53 DOMPurify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-109344: DOMPurify cross-site scripting in IN_PLACE mode with afterSanitize hooks

CVE-2026-109344 · Severity: medium · CVSS 6.1 · Published 2026-10-12

DOMPurify is a JavaScript library that sanitizes HTML to prevent malicious code execution. When using IN_PLACE mode with certain hooks, the library fails to neutralize event handlers on DOM elements removed during sanitization, leaving them armed on the live page. An attacker can supply markup with malicious event handlers that survive the sanitization process and execute in the victim's browser.

Technologies: Cure53 DOMPurify. Vendors: Cure53.

Quick answers

Is CVE-2026-109344 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-109344 being exploited in the wild.
How severe is CVE-2026-109344?: Medium severity, with a CVSS score of 6.1, published 12 October 2026.
Which products and versions are affected?: Cure53 DOMPurify 3.4.13 through 3.4.15.
Is there a fix for CVE-2026-109344?: Yes: fixed in 3.4.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-109344 attacked?: It is attacked over the network.
Am I affected by CVE-2026-109344?: Check whether you run Cure53 DOMPurify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.4.16

Technical details

A cross-site scripting vulnerability exists when IN_PLACE mode processes markup and an afterSanitizeElements or afterSanitizeAttributes hook removes a non-root element; the library's neutralization routine is only wired into beforeSanitizeElements and uponSanitizeElement hooks, leaving descendant on* handlers armed on detached subtrees. An attacker supplies markup containing event handlers (e.g., <img onerror>) inside a wrapper element that a removal hook detaches; after sanitize() returns, the queued handler fires in the victim's page origin, achieving DOM XSS. A fix is available in version 3.4.16.

Affected products

cure53 DOMPurify 3.4.13 through 3.4.15

Timeline

2026-09-23: disclosed
2026-10-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.