CVE-2025-26791 is a medium-severity (CVSS 4.5) Cross-site Scripting (XSS) vulnerability in dompurify. A fix is available for dompurify — see the affected versions and patch details below.
DOMPurify allows Cross-site Scripting (XSS)
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-26791.
EPSS Exploitation Probability
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-2025-26791 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,636 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
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.
dompurifynpmDescription
DOMPurify before 3.2.4 has an incorrect template literal regular expression when SAFE_FOR_TEMPLATES is set to true, sometimes leading to mutation cross-site scripting (mXSS).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dompurify | all versions | 3.2.4npm install dompurify@3.2.4 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update dompurify to 3.2.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-26791 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-26791 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-26791. 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.5 for RHEL 8 | automation-gateway-0:2.5.20250312-1.el8ap | RHSA-2025:2518 |
| Red Hat Ceph Storage 7.1 | ceph-2:18.2.1-381.el8cp | RHSA-2026:2769 |
| Red Hat OpenShift Service Mesh 2.5 for RHEL 8 | openshift-service-mesh/kiali-ossmc-rhel8:1.73.18-2 | RHSA-2025:1875 |
| Red Hat Ceph Storage 8 | rhceph/grafana-rhel9:1770630607 | RHSA-2026:2737 |
| Red Hat Ceph Storage 9 | rhceph/grafana-rhel10:1771399331 | RHSA-2026:3406 |
| Red Hat Developer Hub 1.6 | rhdh/rhdh-hub-rhel9:1.6.0-1745956724 | RHSA-2025:7626 |
| Red Hat OpenShift AI 2.16 | rhoai/odh-dashboard-rhel8:v2.16.2-1741963152 | RHSA-2025:3368 |
| Red Hat OpenShift AI 2.16 | rhoai/odh-dashboard-rhel8:v2.16.2-1741963152 | RHSA-2025:3397 |
Frequently Asked Questions
Is CVE-2025-26791 in your dependencies?
O3 Security finds CVE-2025-26791 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.