CVE-2026-65900

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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 after adjacent text nodes merge survive sanitization. This bypasses SAFE_FOR_TEMPLATES and can allow a downstream template engine to evaluate attacker-supplied expressions. The string output path is not affected.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 23, 2026

Last Modified

July 28, 2026

Advisory Details (2)

Auto-updated Jul 23, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

DOMPurify before 3.4.8 Template Expression Injection via RETURN_DOM | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-template-expression-injection-via-return-dom
github Patch Available🟡 PoC Available

SAFE_FOR_TEMPLATES bypass - template expressions survive sanitization inside <template> content when using DOM output modes · Advisory · cure53/DOMPurify · GitHub

https://github.com/cure53/DOMPurify/security/advisories/GHSA-gvmj-g25r-r7wr

Vendor Advisories for CVE-2026-65900(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-dompurify2.4.1+dfsg+~2.4.0-1 ... 3.4.5+dfsg-1 (15 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (9 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (8 versions)3.4.12+dfsg-1—
npm(1)
PackageVulnerable rangeFixed inDependents
dompurify—3.4.8—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 03:47 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 02:35 UTCEG score recompute
  4. 2026-08-24 01:24 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-23 00:11 UTCEG score recompute
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-19 20:34 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 19:00 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 15:08 UTCEG score recompute
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 13:57 UTCEG score recompute
  16. 2026-08-15 12:46 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 11:31 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 10:20 UTCEG score recompute
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-12 09:08 UTCEG score recompute
  23. 2026-08-11 07:56 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 06:45 UTCEG score recompute
Show 33 more
  1. 2026-08-09 13:47 UTCEPSS rescore
  2. 2026-08-09 05:34 UTCEG score recompute
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-08 04:23 UTCEG score recompute
  5. 2026-08-07 03:11 UTCEG score recompute
  6. 2026-08-06 13:47 UTCEPSS rescore
  7. 2026-08-06 02:00 UTCEG score recompute
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-05 19:17 UTCEPSS rescore
  10. 2026-08-05 00:49 UTCEG score recompute
  11. 2026-08-04 15:10 UTCEPSS rescore
  12. 2026-08-04 10:39 UTCEPSS rescore
  13. 2026-08-03 23:37 UTCEG score recompute
  14. 2026-08-03 10:36 UTCEPSS rescore
  15. 2026-08-02 22:26 UTCEG score recompute
  16. 2026-08-02 02:27 UTCEPSS rescore
  17. 2026-07-30 18:49 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-30 01:30 UTCEPSS rescore
  20. 2026-07-28 15:59 UTCEG score recompute
  21. 2026-07-28 15:37 UTCEPSS rescore
  22. 2026-07-28 05:40 UTCEG score recompute
  23. 2026-07-27 14:14 UTCEPSS rescore
  24. 2026-07-27 04:24 UTCEG score recompute
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-26 03:09 UTCEG score recompute
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-25 14:18 UTCEPSS rescore
  30. 2026-07-24 14:18 UTCEPSS rescore
  31. 2026-07-24 14:18 UTCEPSS rescore
  32. 2026-07-23 13:25 UTCEG score recompute
  33. 2026-07-23 13:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-65900?
CVE-2026-65900 is a medium vulnerability published on July 23, 2026. DOMPurify versions >=3.0.0 and before 3.4.8, when configured with SAFEFORTEMPLATES together with a DOM output mode (RETURNDOM, RETURNDOMFRAGMENT, or INPLACE), fail to strip template expressions (e.g. ${evil}, {{evil}}, <%evil%>) inside <template> element content. The final normalization/scrub pass…
When was CVE-2026-65900 disclosed?
CVE-2026-65900 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65900 actively exploited?
CVE-2026-65900 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.1% of all scored CVEs.
What is the CVSS score of CVE-2026-65900?
CVE-2026-65900 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65900?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65900, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65900

Explore →

Is Your Infrastructure Affected by CVE-2026-65900?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs