CVE-2026-65011

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-07-22. the CNA's CVSS baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

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

Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/{definitionId}/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private event definitions including detection queries, aggregation thresholds, grouping fields, schedules, and notification bindings by duplicating them.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

July 22, 2026

Last Modified

July 24, 2026

Advisory Details (6)

Auto-updated Jul 22, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Graylog2 Server Missing Permission Check on Event Definition Duplicate | Advisories | VulnCheck

https://www.vulncheck.com/advisories/graylog2-server-missing-permission-check-on-event-definition-duplicate
github_pr

Add read permission check on Event definition for duplicate (`7.0`)

Fix merged in Graylog2/graylog2-server PR #26719 on 2026-07-22 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26719
github_pr

Add read permission check on Event definition for duplicate (`7.1`)

Fix merged in Graylog2/graylog2-server PR #26718 on 2026-07-22 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26718
github_pr

Add read permission check on Event definition for duplicate

Fix merged in Graylog2/graylog2-server PR #26706 on 2026-07-21 — awaiting tagged release

https://github.com/Graylog2/graylog2-server/pull/26706
generic

Missing per-entity permission check on Event Definition duplicate endpoint allows reading any user's private alert configuration · Issue #26590 · Graylog2/graylog2-server · GitHub

https://github.com/Graylog2/graylog2-server/issues/26590
github_commit

commit 46a2eeba4cdb (Graylog2/graylog2-server)

Fix landed in Graylog2/graylog2-server commit 46a2eeba4cdb — awaiting tagged release

https://github.com/Graylog2/graylog2-server/commit/46a2eeba4cdbc1408ff4cbf7b466853a8acfb38d

Vendor Advisories for CVE-2026-65011(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 41× 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-03 18:58 UTCEG score recompute
  2. 2026-08-03 18:58 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-02 17:04 UTCEG score recompute
  5. 2026-08-02 17:04 UTCGHSA enrichment
  6. 2026-08-02 02:27 UTCEPSS rescore
  7. 2026-08-01 15:10 UTCEG score recompute
  8. 2026-08-01 15:10 UTCGHSA enrichment
  9. 2026-08-01 04:16 UTCEPSS rescore
  10. 2026-07-31 13:16 UTCEG score recompute
  11. 2026-07-31 13:16 UTCGHSA enrichment
  12. 2026-07-30 16:28 UTCEPSS rescore
  13. 2026-07-30 11:21 UTCEG score recompute
  14. 2026-07-30 11:21 UTCGHSA enrichment
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-30 01:30 UTCEPSS rescore
  17. 2026-07-29 09:25 UTCEG score recompute
  18. 2026-07-29 09:25 UTCGHSA enrichment
  19. 2026-07-28 15:37 UTCEPSS rescore
  20. 2026-07-28 07:30 UTCEG score recompute
  21. 2026-07-28 07:30 UTCGHSA enrichment
  22. 2026-07-27 14:14 UTCEPSS rescore
  23. 2026-07-27 05:32 UTCEG score recompute
  24. 2026-07-27 05:31 UTCGHSA enrichment
  25. 2026-07-26 14:54 UTCEPSS rescore
Show 16 more
  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 03:27 UTCEG score recompute
  3. 2026-07-26 03:26 UTCGHSA enrichment
  4. 2026-07-25 14:18 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:22 UTCEG score recompute
  11. 2026-07-22 21:10 UTCEG score recompute
  12. 2026-07-22 21:09 UTCGHSA enrichment
  13. 2026-07-22 18:40 UTCEG score recompute
  14. 2026-07-22 18:39 UTCGHSA enrichment
  15. 2026-07-22 16:31 UTCEG score recompute
  16. 2026-07-22 16:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65011?
CVE-2026-65011 is a medium vulnerability published on July 22, 2026. Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/{definitionId}/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private…
When was CVE-2026-65011 disclosed?
CVE-2026-65011 was first published in the National Vulnerability Database on July 22, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65011 actively exploited?
CVE-2026-65011 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 87.7% of all scored CVEs.
What is the CVSS score of CVE-2026-65011?
CVE-2026-65011 has a CVSS v4.0 base score of 4.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-65011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65011, 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

Explore the affected products and dependency analysis for CVE-2026-65011

Explore →

Is Your Infrastructure Affected by CVE-2026-65011?

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