CVE-2026-109345: DOMPurify before 3.4.16 XSS via IN_PLACE Returned Rawtext Root

Published Oct 12, 2026
·
Updated

DOMPurify before 3.4.16 contains a cross-site scripting vulnerability that allows attackers to bypass sanitization because INPLACE mode returns a force-removed style element whose text content still carries markup. Attackers can supply a style element containing a closing style tag and an img onerror payload, which executes script when the application serializes and re-parses the returned node.

Affected Software

3 affected componentsFixes available
npm/dompurify<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 applications are exposed to this issue?

Applications using the npm dompurify package before version 3.4.16 are exposed when they use IN_PLACE mode and later serialize and re-parse the returned node. The issue requires attacker-controlled HTML to reach that sanitization flow.

2

What does an attacker need to do to trigger script execution?

An attacker must supply a style element whose text includes a closing style tag followed by an img element with an onerror payload. Script execution occurs when the application serializes and then re-parses the node returned by DOMPurify.

3

Is user interaction required?

Yes. The supplied CVSS vector specifies UI:R, meaning user interaction is required. The vector also indicates that no attacker privileges are required and the issue can be reached over the network.

4

What is the remediation?

Upgrade DOMPurify to version 3.4.16 or later. If upgrading cannot happen immediately, avoid using IN_PLACE mode for attacker-controlled HTML and do not serialize and re-parse nodes returned from that mode.

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