Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2024-47875 dompurify

CRITICALFix: cure53/DOMPurify@0ef5e53

CVE-2024-47875 is a critical-severity (CVSS 10) Cross-site Scripting (XSS) vulnerability in dompurify. A fix is available for dompurify — see the affected versions and patch details below.

DOMPurify nesting-based mXSS

Also known asGHSA-gx9m-whjm-85jf
Published
Oct 11, 2024
Updated
Aug 12, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47875.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-47875 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

5Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
dompurifynpm
46.1Mdownloads / week

Description

DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMpurify was vulnerable to nesting-based mXSS. This vulnerability is fixed in 2.5.0 and 3.1.3.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmdompurifyall versions2.5.0npm install dompurify@2.5.0
📦npmdompurify3.0.0&&< 3.1.33.1.3npm install dompurify@3.1.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dompurify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update dompurify to 2.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-47875 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-47875 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-47875. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat Enterprise Linux 8grafana-0:9.2.10-20.el8_10RHSA-2024:8327
Red Hat Enterprise Linux 9grafana-0:9.2.10-19.el9_4RHSA-2024:8678
Red Hat Enterprise Linux 9grafana-0:10.2.6-7.el9_5RHSA-2024:9473
Red Hat OpenShift Container Platform 4.14openshift4/ose-monitoring-plugin-rhel8:v4.14.0-202411130434.p0.gb57ebe7.assembly.stream.el8RHSA-2024:9620
Red Hat OpenShift Container Platform 4.15openshift4/ose-monitoring-plugin-rhel8:v4.15.0-202411060036.p0.ge40b085.assembly.stream.el8RHSA-2024:8991
Red Hat OpenShift Container Platform 4.16openshift4/ose-monitoring-plugin-rhel9:v4.16.0-202410300036.p0.g442ccd1.assembly.stream.el9RHSA-2024:8683
Red Hat OpenShift Container Platform 4.17openshift4/ose-monitoring-plugin-rhel9:v4.17.0-202410300235.p0.g9c9c0a0.assembly.stream.el9RHSA-2024:8981
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/code-rhel8:3.17-19RHSA-2024:10236

Frequently Asked Questions

DOMPurify is a DOM-only, super-fast, uber-tolerant XSS sanitizer for HTML, MathML and SVG. DOMpurify was vulnerable to nesting-based mXSS. This vulnerability is fixed in 2.5.0 and 3.1.3.
O3 Security · Impact-Aware SCA

Is CVE-2024-47875 in your dependencies?

O3 Security finds CVE-2024-47875 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2024-47875: dompurify XSS (Critical 10) | O3 Security