Skip to content
OpenAdvisories

Description

DOMPurify before 3.4.12 fails to execute afterSanitizeElements hook for custom elements allowed via CUSTOM_ELEMENT_HANDLING.tagNameCheck, allowing attributes to bypass application security policies. Attackers can preserve sensitive attributes on custom elements that later re-inject them into innerHTML sinks, creating second-order XSS gadgets.

Affected products

VendorProductAffectedFixed
cure53 DOMPurify < 3.4.12 3.4.12

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 node-dompurify 3.4.12+dfsg-1 —
Debian 13 node-dompurify No fix yet —
Debian 12 node-dompurify No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.04 LTS node-dompurify No fix yet —
Ubuntu 24.04 LTS node-dompurify No fix yet —
Ubuntu 22.04 LTS node-dompurify No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling jupyter-base-notebook 7.6.3-r2 —
Wolfi rolling langfuse-3-compat 3.225.7-r6 —
Wolfi rolling langfuse-3-worker 3.224.1-r0 —
Wolfi rolling nextcloud-server-33 33.0.7-r5 —
Wolfi rolling opensearch-dashboards-3 +12 3.7.0-r7 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm dompurify < 3.4.12 3.4.12 GHSA-c2j3-45gr-mqc4

Advisories 1

References