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
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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 |
Affected Products
dompurifycure53Detection & 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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
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 Ceph Storage 9.2 | rhceph/rhceph-9-rhel10:1790843527 | RHSA-2026:86618 |
| 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 |
Frequently Asked Questions
Is CVE-2025-26791 in your dependencies?
Find it across npm, including transitive dependencies.