CVE-2026-65900: DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFE_FOR_TEMPLATES together with a DOM outpu

Routine

MEDIUM 6.1UPGRADE

CVE-2026-65900 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.

DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFE_FOR_TEMPLATES together with a DOM output mode (RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE), fail to strip template expressions (e.g. ${evil}, {{evil}}, <%evil%>) inside <template> element content. The final normalization/scrub pass (_scrubTemplateExpressions) uses a NodeIterator and node.normalize() that do not descend into template.content, so expressions that only form aft

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 77%)
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.0.0 and < 3.4.8

Fixed in: 3.4.8

Safe to downgrade to: a release before 3.0.0

1. Check installed version

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

2. UPGRADE to 3.4.8 (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.

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison dompurify sudo apt install dompurify=<VERSION_BEFORE_3.0.0> sudo apt-mark hold dompurify

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list dompurify sudo dnf downgrade dompurify-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add dompurify

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

npm · dompurify · FIXED · 3.4.8 · vulnerable: >= 3.0.0, <= 3.4.7 · source

npm install dompurify@">=3.4.8" npm ls dompurify

Fedora 46 · sugar-clock · FIXED · 22.1-17.fc46 · FEDORA-2026-57948849df · source

sudo dnf upgrade --advisory=FEDORA-2026-57948849df

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 · NOT AFFECTED

RHEL 10 · cockpit-image-builder · DEFERRED

RHEL 10 · grafana · DEFERRED

RHEL 10 · grafana-pcp · DEFERRED

RHEL 8 · grafana · NOT AFFECTED

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-gvmj-g25r-r7wr

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-65900?

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

Is CVE-2026-65900 being exploited?

CVE-2026-65900 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-65900 affect?

CVE-2026-65900 affects dompurify. Severity is medium (CVSS 6.1). DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFE_FOR_TEMPLATES together with a DOM output mode (RETURN_DOM, RETURN_DOM_FRAGMENT, or IN_PLACE), fail to strip template expressions (e.g. ${evil}, {{evil}}, <%evil%>) insid

How urgent is CVE-2026-65900?

Priority 32/100. Public exploit reference

Related CVEs

CVE-2026-47423 HIGH 8.2 DOWNGRADE DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG
CVE-2026-49458 MEDIUM 6.1 UPGRADE DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG
CVE-2026-49978 MEDIUM 6.1 UPGRADE DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG
CVE-2026-49459 MEDIUM 6.1 UPGRADE DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG
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

References

← Back to latest CVEs