CVE-2026-109344: DOMPurify from 3.4.13 before 3.4.16 DOM XSS via IN_PLACE afterSanitize Hooks

Published Oct 12, 2026
·
Updated

DOMPurify from 3.4.13 before 3.4.16 contains a cross-site scripting vulnerability because INPLACE 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.

Affected Software

3 affected componentsFixes available
npm/dompurify>=3.4.13<3.4.16
IBM Db2 Genius Hub<=1.1.2, 1.1.3, 1.1.4, 1.1.5
IBM Agentics<=1.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade DOMPurify to a version that resolves this vulnerability.

    Fixed in 3.4.16

Event History

Oct 12, 2026
CVE Published
via MITRE·04:05 PM
Data Sourced
via MITRE·04:05 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Nov 3, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using DOMPurify versions 3.4.13 through 3.4.15 are exposed when they use IN_PLACE mode together with afterSanitizeElements or afterSanitizeAttributes hooks that detach subtrees. The issue concerns markup processed through that configuration.

2

What does an attacker need to exploit the vulnerability?

An attacker needs to be able to supply markup that is sanitized by the affected DOMPurify configuration. The supplied markup can contain on* event handlers inside a wrapper that an after-sanitization hook removes, and exploitation requires victim interaction.

3

What is the practical impact?

Event handlers can remain armed on the live DOM after the hook detaches their enclosing subtree. If triggered, they can execute script in the victim's origin.

4

How can I determine whether my application is affected?

Check whether your application uses DOMPurify 3.4.13, 3.4.14, or 3.4.15, invokes sanitize with IN_PLACE mode, and registers afterSanitizeElements or afterSanitizeAttributes hooks that remove or detach DOM subtrees. All of those conditions are relevant to this issue.

5

What can be done if upgrading is not immediately possible?

Avoid the affected combination of IN_PLACE mode and afterSanitizeElements or afterSanitizeAttributes hooks that detach subtrees. Update DOMPurify to version 3.4.16 or later when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203