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.3% (24th percentile of EPSS-scored CVEs). 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 — 3 sources updated 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.3%CVSS: 6.1Exploit: None knownExposed services: Not assessed

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.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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
githubMentions a patch (unverified)🟡 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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
node-dompurify2.4.1+dfsg+~2.4.0-1 ... 3.4.5+dfsg-1 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-dompurify3.1.7+dfsg+~3.0.5-2 ... 3.4.5+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
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-2
  • every version up to 3.4.1+dfsg-1: fixed in 3.4.1+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 47× 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.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 08:21 UTCEG score recompute
  8. 2026-10-04 08:21 UTCVendor advisory
  9. 2026-10-03 14:26 UTCEPSS rescore
  10. 2026-10-03 03:25 UTCEG score recompute
  11. 2026-10-03 03:25 UTCVendor advisory
  12. 2026-10-02 17:56 UTCEPSS rescore
  13. 2026-10-01 19:50 UTCEPSS rescore
  14. 2026-10-01 06:17 UTCEG score recompute
  15. 2026-10-01 06:17 UTCVendor advisory
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-28 13:51 UTCEPSS rescore
  18. 2026-09-28 05:06 UTCEG score recompute
  19. 2026-09-28 05:06 UTCVendor advisory
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-24 01:16 UTCEG score recompute
  22. 2026-09-24 01:16 UTCVendor advisory
  23. 2026-09-23 17:54 UTCEPSS rescore
  24. 2026-09-22 22:43 UTCEG score recompute
  25. 2026-09-22 22:43 UTCVendor advisory
Show 75 more
  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 01:47 UTCEG score recompute
  3. 2026-09-20 01:47 UTCVendor advisory
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 10:47 UTCEG score recompute
  6. 2026-09-18 10:47 UTCVendor advisory
  7. 2026-09-17 09:17 UTCEG score recompute
  8. 2026-09-17 09:17 UTCVendor advisory
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 06:48 UTCEG score recompute
  11. 2026-09-16 06:48 UTCVendor advisory
  12. 2026-09-16 05:15 UTCEPSS rescore
  13. 2026-09-13 22:23 UTCEG score recompute
  14. 2026-09-13 22:23 UTCVendor advisory
  15. 2026-09-12 18:23 UTCEG score recompute
  16. 2026-09-12 18:23 UTCVendor advisory
  17. 2026-09-11 16:45 UTCEG score recompute
  18. 2026-09-11 16:45 UTCVendor advisory
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-10 15:11 UTCEG score recompute
  22. 2026-09-10 15:11 UTCVendor advisory
  23. 2026-09-09 08:57 UTCEG score recompute
  24. 2026-09-09 08:57 UTCVendor advisory
  25. 2026-09-08 22:01 UTCEPSS rescore
  26. 2026-09-07 21:31 UTCEG score recompute
  27. 2026-09-07 21:31 UTCVendor advisory
  28. 2026-09-07 16:01 UTCEPSS rescore
  29. 2026-09-06 13:47 UTCEPSS rescore
  30. 2026-09-05 19:28 UTCEG score recompute
  31. 2026-09-05 19:28 UTCVendor advisory
  32. 2026-09-05 15:31 UTCEPSS rescore
  33. 2026-09-04 13:16 UTCEG score recompute
  34. 2026-09-04 13:16 UTCVendor advisory
  35. 2026-09-04 05:07 UTCEPSS rescore
  36. 2026-09-02 14:12 UTCEPSS rescore
  37. 2026-09-01 23:22 UTCEG score recompute
  38. 2026-09-01 23:22 UTCVendor advisory
  39. 2026-09-01 13:54 UTCEPSS rescore
  40. 2026-09-01 04:40 UTCEPSS rescore
  41. 2026-08-31 01:58 UTCEG score recompute
  42. 2026-08-31 01:58 UTCVendor advisory
  43. 2026-08-30 19:17 UTCEPSS rescore
  44. 2026-08-30 01:22 UTCEPSS rescore
  45. 2026-08-30 00:34 UTCEG score recompute
  46. 2026-08-30 00:34 UTCVendor advisory
  47. 2026-08-28 21:42 UTCEPSS rescore
  48. 2026-08-27 10:10 UTCEG score recompute
  49. 2026-08-27 10:10 UTCVendor advisory
  50. 2026-08-26 14:47 UTCEPSS rescore
  51. 2026-08-26 07:50 UTCEG score recompute
  52. 2026-08-26 07:50 UTCVendor advisory
  53. 2026-08-25 13:49 UTCEPSS rescore
  54. 2026-08-25 06:13 UTCEG score recompute
  55. 2026-08-25 06:13 UTCVendor advisory
  56. 2026-08-24 04:49 UTCVendor advisory
  57. 2026-08-23 03:24 UTCEG score recompute
  58. 2026-08-23 03:24 UTCVendor advisory
  59. 2026-08-23 00:19 UTCEPSS rescore
  60. 2026-08-22 02:00 UTCEG score recompute
  61. 2026-08-22 02:00 UTCVendor advisory
  62. 2026-08-21 23:49 UTCEPSS rescore
  63. 2026-08-21 00:36 UTCEG score recompute
  64. 2026-08-20 22:56 UTCEPSS rescore
  65. 2026-08-19 23:12 UTCEG score recompute
  66. 2026-08-19 17:04 UTCEPSS rescore
  67. 2026-08-18 21:48 UTCEG score recompute
  68. 2026-08-18 13:48 UTCEPSS rescore
  69. 2026-08-17 20:24 UTCEG score recompute
  70. 2026-08-17 13:47 UTCEPSS rescore
  71. 2026-08-16 17:11 UTCEG score recompute
  72. 2026-08-16 14:56 UTCEPSS rescore
  73. 2026-08-15 15:47 UTCEG score recompute
  74. 2026-08-15 01:30 UTCEPSS rescore
  75. 2026-08-14 14:23 UTCEG score recompute

Related CVEs(same product + 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 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.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65911?
CVE-2026-65911 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65911?
A fix for CVE-2026-65911 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65911 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs