CVE-2026-65911

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 86% 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
Trending — Patch released this week
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: None knownExposed: 0

A fix is available — apply it.

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 tags. This can allow dangerous event-handler attributes or forbidden tags (bypassing FORBID_TAGS) to survive sanitization, resulting in cross-site scripting. The vendor (Cure53) considers this an edge case outside DOMPurify's threat model; the referenced advisory lists 3.4.0 as the patched version.

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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
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.0 XSS via ADD_ATTR/ADD_TAGS State Leakage | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dompurify-before-xss-via-add-attr-add-tags-state-leakage
github Patch Available🟡 PoC Available

XSS via ADD_ATTR/ADD_TAGS Function Predicate State Leakage Across sanitize() Calls · Advisory · cure53/DOMPurify · GitHub

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

Vendor Advisories for CVE-2026-65911(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana12-4-main-12.4.8-0.1.2.hum12026-08-22redhat
redhatgrafana13-1-main-13.1.3-0.1.1.hum12026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 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.2.5+dfsg-1, 3.3.2+dfsg-1, 3.3.3+dfsg-1, 3.3.3+dfsg-23.4.1+dfsg-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 58× 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 07:50 UTCEG score recompute
  2. 2026-08-26 07:50 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 06:13 UTCEG score recompute
  5. 2026-08-25 06:13 UTCVendor advisory
  6. 2026-08-24 04:49 UTCVendor advisory
  7. 2026-08-23 03:24 UTCEG score recompute
  8. 2026-08-23 03:24 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 02:00 UTCEG score recompute
  11. 2026-08-22 02:00 UTCVendor advisory
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-21 00:36 UTCEG score recompute
  14. 2026-08-20 22:56 UTCEPSS rescore
  15. 2026-08-19 23:12 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 21:48 UTCEG score recompute
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 20:24 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 17:11 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-15 15:47 UTCEG score recompute
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 14:23 UTCEG score recompute
Show 43 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 12:59 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-12 11:36 UTCEG score recompute
  5. 2026-08-11 10:12 UTCEG score recompute
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 08:49 UTCEG score recompute
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-09 07:25 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 06:02 UTCEG score recompute
  12. 2026-08-07 04:38 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-06 03:14 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 01:50 UTCEG score recompute
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 10:39 UTCEPSS rescore
  20. 2026-08-04 00:27 UTCEG score recompute
  21. 2026-08-03 10:36 UTCEPSS rescore
  22. 2026-08-02 23:01 UTCEG score recompute
  23. 2026-08-02 02:27 UTCEPSS rescore
  24. 2026-08-01 21:37 UTCEG score recompute
  25. 2026-08-01 04:16 UTCEPSS rescore
  26. 2026-07-30 18:49 UTCEG score recompute
  27. 2026-07-30 16:28 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-28 15:59 UTCEG score recompute
  30. 2026-07-28 15:37 UTCEPSS rescore
  31. 2026-07-27 17:21 UTCEG score recompute
  32. 2026-07-27 17:02 UTCEG score recompute
  33. 2026-07-27 14:14 UTCEPSS rescore
  34. 2026-07-27 04:33 UTCEG score recompute
  35. 2026-07-26 14:54 UTCEPSS rescore
  36. 2026-07-26 14:54 UTCEPSS rescore
  37. 2026-07-26 03:07 UTCEG score recompute
  38. 2026-07-25 14:18 UTCEPSS rescore
  39. 2026-07-25 14:18 UTCEPSS rescore
  40. 2026-07-24 14:18 UTCEPSS rescore
  41. 2026-07-24 14:18 UTCEPSS rescore
  42. 2026-07-23 13:25 UTCEG score recompute
  43. 2026-07-23 13:24 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-65911?
CVE-2026-65911 is a medium vulnerability published on July 23, 2026. In DOMPurify through 3.3.3, function predicates supplied via ADDATTR or ADDTAGS to DOMPurify.sanitize() persist in internal state (EXTRAELEMENTHANDLING) across subsequent sanitize() calls on the same instance. If a later call on the same instance provides ADDATTR or ADDTAGS as an array rather than…
When was CVE-2026-65911 disclosed?
CVE-2026-65911 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-65911 actively exploited?
CVE-2026-65911 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 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-65911?
CVE-2026-65911 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-65911?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65911, 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-65911

Explore →

Is Your Infrastructure Affected by CVE-2026-65911?

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

Start Free Scan →Browse All CVEs