DOMPurify allows tampering by prototype pollution (CVE-2024-45801) | HOL Guard CVE

High · CVSS 7.0CVE-2024-45801GHSA-MMHX-HMJR-R674

DOMPurify allows tampering by prototype pollution

Answer in brief

CVE-2024-45801 records a High severity (CVSS 7.0) vulnerability in DOMPurify allows tampering by prototype pollution. The current sources do not mark it as known exploited. The current feed maps dompurify (npm), dompurify (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2024Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.0
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps dompurify (npm), dompurify (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
dompurifynpm	>=0 <2.5.4	2.5.4
dompurifynpm	>=3.0.0 <3.1.3	3.1.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for dompurify, dompurify.
Review the reported fix. Update dompurify to 2.5.4; dompurify to 3.1.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2024
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

It has been discovered that malicious HTML using special nesting techniques can bypass the depth checking added to DOMPurify in recent releases. It was also possible to use Prototype Pollution to weaken the depth check. This renders dompurify unable to avoid XSS attack. Fixed by https://github.com/cure53/DOMPurify/commit/1e520262bf4c66b5efda49e2316d6d1246ca7b21 (3.x branch) and https://github.com/cure53/DOMPurify/commit/26e1d69ca7f769f5c558619d644d90dd8bf26ebc (2.x branch).

Quoted source text, attributed separately from HOL analysis.