VulertSecurity VulertSecurity

Vulnerability Database · npm · dompurify · Version

dompurify 2.5.2

2.5.2 is affected by 21 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 2 Medium 14 Low 5 Unrated 0

All dompurify versions & vulnerabilities → Source repository Search the database for this package →
Released 30 Apr 2024 Licence Apache-2.0 OR MPL-2.0 Also known from other sources 18 Newer releases 154 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

dompurify 2.5.2 vulnerabilities

21 vulnerabilities cover dompurify 2.5.2. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
GHSA-mrv2-3pqr-j5jr: DOMPurify IN_PLACE hooks can leave detached event handlers active 7.6 high 3.4.17 22 Oct 2026
CVE-2024-45801: DOMPurify Prototype Pollution Vulnerability Leading to XSS Risks 7.0 high 2.5.4 16 Sep 2024
Mutation-XSS Vulnerability in DOMPurify: A Security Risk for Sanitized HTML 6.9 medium 3.3.2 27 Mar 2026
CVE-2026-41239: DOMPurify SAFE_FOR_TEMPLATES Bypass in RETURN_DOM Mode 6.8 medium 3.4.0 22 Apr 2026
DOMPurify Vulnerability: CUSTOM_ELEMENT_HANDLING Bypass in Version 3.4.11 6.1 medium No fix published 24 Jul 2026
Persistent Pollution Vulnerability in DOMPurify: Hook Mutation of Allowed Tags and Attributes 6.1 medium 3.4.7 15 Jun 2026
CVE-2026-49458: DOMPurify Cross-Realm IN_PLACE Sanitization Vulnerability 6.1 medium 3.4.6 15 Jun 2026
CVE-2026-49459: DOMPurify XSS Vulnerability via IN_PLACE Mode Attribute Preservation 6.1 medium 3.4.6 15 Jun 2026
CVE-2026-41240: DOMPurify Vulnerability Allows Bypass of FORBID_TAGS with Function-Based ADD_TAGS 6.0 medium 3.4.0 22 Apr 2026
DOMPurify Package Vulnerability: Bypass of FORBID_TAGS via ADD_TAGS Function 5.3 medium 3.4.0 16 Apr 2026
DOMPurify Vulnerability: URI Validation Bypass in ADD_ATTR Predicate 5.3 medium 3.3.2 03 Apr 2026
Prototype Pollution in DOMPurify Allows Bypass of Event Handler Restrictions 5.3 medium 3.3.2 03 Apr 2026
XSS Vulnerability in DOMPurify: Risk of Executable Detached Subtree 5.1 medium 3.4.13 07 Aug 2026
Persistent ALLOWED_ATTR Pollution in DOMPurify: A Security Flaw 5.1 medium 3.4.11 18 Jun 2026
CVE-2026-49978: DOMPurify Sanitization Bypass via Shadow DOM in <template> 5.1 medium 3.4.7 15 Jun 2026
DOMPurify XSS Vulnerability - Cross-site Scripting Risk in dompurify Package 4.5 medium 3.2.4 14 Feb 2025
DOMPurify Custom Element Handling Bypass Vulnerability - CVE-2026-XXXX 2.1 low 3.4.12 21 Jul 2026
DOMPurify Vulnerability: Trusted Types Policy Persistence After Clear Config 2.1 low 3.4.9 15 Jun 2026
GHSA-c6gr-qvv4-5v3f: DOMPurify XHTML-mode SVG sanitization allows click-triggered XSS N/A low 3.4.17 22 Oct 2026
DOMPurify Vulnerability: IN_PLACE Mode Allows Rawtext Payload Execution N/A low 3.4.16 05 Oct 2026
XSS Vulnerability in DOMPurify 3.4.6: Trusting Attacker-Controlled Node Names N/A low No fix published 15 Jun 2026

Looking for another version, or everything Vulert holds for dompurify?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About dompurify 2.5.2

Is dompurify 2.5.2 vulnerable?

Yes. 21 vulnerabilities in the Vulert database cover dompurify 2.5.2: 0 critical, 2 high, 14 medium and 5 low. Each entry above names the fixed version to move to.

Is 2.5.2 the latest release of dompurify?

No. 2.5.2 was published 30 Apr 2024, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor dompurify for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the dompurify version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.