CVE-2026-65913: cure53 DOMPurify prototype pollution in USE_PROFILES mode

CVE-2026-65913 · Severity: medium · CVSS 6.1 · Published 2026-07-23

DOMPurify, a widely used library for cleaning up malicious code from web pages, contains a security flaw when using its 'profiles' feature. An attacker can exploit this to bypass security filters and inject malicious scripts into a website. This could lead to unauthorized actions being performed in a user's browser, such as stealing session information or redirecting users to malicious sites.

Technologies: dompurify (npm). Vendors: npm.

Quick answers

Is CVE-2026-65913 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-65913 being exploited in the wild.
How severe is CVE-2026-65913?
Medium severity, with a CVSS score of 6.1, published 23 July 2026.
Which products and versions are affected?
dompurify (npm) <= 3.3.1, SEMVER:introduced=0,fixed=3.3.2.
Is there a fix for CVE-2026-65913?
Yes. dompurify (npm): upgrade to 3.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65913 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-65913?
Check whether you run dompurify (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • dompurify (npm): upgrade to 3.3.2 or later
    npm install dompurify@3.3.2

Technical details

A prototype pollution vulnerability exists in DOMPurify when the USE_PROFILES configuration is enabled. In this mode, the library rebuilds its internal attribute allowlist (ALLOWED_ATTR) as a plain array but continues to perform lookups using bracket notation. If an attacker can pollute Array.prototype (e.g., setting Array.prototype.onclick = true), the sanitizer will incorrectly identify dangerous event handlers as allowlisted attributes. This bypass allows malicious event handlers to survive the sanitization process, leading to DOM-based Cross-Site Scripting (XSS) when the output is rendered. The issue is fixed in version 3.3.2.

Affected products

  • cure53 DOMPurify < 3.3.2

Identifiers

  • CVE-2026-65913
  • GHSA-cj63-jhhr-wcxv

Timeline

  • 2026-04-01: advisory: GitHub Security Advisory published
  • 2026-07-23: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.