CVE-2026-65911: In DOMPurify through 3.3.3, function predicates supplied via ADD_ATTR or ADD_TAGS to DOMPurify.sanitize() pers

Q: How do I fix CVE-2026-65911?

dompurify: upgrade to 3.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-65911 being exploited?

CVE-2026-65911 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-65911 affect?

CVE-2026-65911 affects dompurify. Severity is medium (CVSS 6.1). In DOMPurify through 3.3.3, function predicates supplied via ADD_ATTR or ADD_TAGS to DOMPurify.sanitize() persist in internal state (EXTRA_ELEMENT_HANDLING) across subsequent sanitize() calls on the same instance. If a later call on the sam

Q: How urgent is CVE-2026-65911?

Priority 33/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2026-65911 is a medium-severity flaw (CVSS 6.1) affecting dompurify. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

In DOMPurify through 3.3.3, function predicates supplied via ADD_ATTR or ADD_TAGS to DOMPurify.sanitize() persist in internal state (EXTRA_ELEMENT_HANDLING) across subsequent sanitize() calls on the same instance. If a later call on the same instance provides ADD_ATTR or ADD_TAGS as an array rather than a function, the previously set function handler is neither cleared nor overwritten, so it continues to approve attacker-controlled attributes or

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 74%)
CISA exploited list	No
Weakness	CWE-79
Published	2026-07-23
Last modified	2026-10-24

Publisher (CNA): VulnCheck · Vendor: cure53

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-23 14:18 UTCPublished CVE record published
2026-10-24 13:10 UTCUpdated Record last modified

cure53 dompurify UPGRADE

Affected: < 3.4.0

Fixed in: 3.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dompurify || rpm -q dompurify || dompurify --version

2. UPGRADE to 3.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dompurify

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dompurify

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Exact fixes by distribution

Fedora 46 · sugar-calculator · FIXED · 47-14.fc46 · FEDORA-2026-38eeb9e279 · source

sudo dnf upgrade --advisory=FEDORA-2026-38eeb9e279

Fedora ELN · selinux-policy · FIXED · 45.23-1.eln159 · FEDORA-2026-3668c969a2 · source

sudo dnf upgrade --advisory=FEDORA-2026-3668c969a2

Debian 12 · node-dompurify · NO FIX YET

Debian 13 · node-dompurify · NO FIX YET

RHEL 10 · ceph · DEFERRED

RHEL 10 · cockpit-image-builder · DEFERRED

RHEL 10 · grafana · DEFERRED

RHEL 10 · grafana-pcp · NOT AFFECTED

RHEL 8 · grafana · DEFERRED

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Write-up: github.com/cure53/DOMPurify/security/advisories/GHSA-9p3w-6h5p-cv75

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-65911?

dompurify: upgrade to 3.4.0. Exact commands for each OS are on this page.

Is CVE-2026-65911 being exploited?

CVE-2026-65911 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-65911 affect?

CVE-2026-65911 affects dompurify. Severity is medium (CVSS 6.1). In DOMPurify through 3.3.3, function predicates supplied via ADD_ATTR or ADD_TAGS to DOMPurify.sanitize() persist in internal state (EXTRA_ELEMENT_HANDLING) across subsequent sanitize() calls on the same instance. If a later call on the sam

How urgent is CVE-2026-65911?

Priority 33/100. Public exploit reference

Related CVEs

CVE-2026-65898 HIGH 7.2 UPGRADE DOMPurify before 3.4.11 fails to clone the ALLOWED_ATTR allowlist when setConfig() is used with an uponSanitiz
CVE-2026-65899 MEDIUM 6.1 UPGRADE DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so
CVE-2026-65902 MEDIUM 6.1 UPGRADE DOMPurify before 3.4.7 (affected versions <= 3.4.5) passes direct references to the module-level DEFAULT_ALLOW
CVE-2026-65900 MEDIUM 6.1 UPGRADE DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFE_FOR_TEMPLATES together with a DOM outpu
CVE-2026-65903 MEDIUM 6.1 UPGRADE DOMPurify before 3.4.0 contains a logic error in the ADD_TAGS function where short-circuit evaluation allows f

References

← Back to latest CVEs