CVE-2026-72650: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user who is authorized to read alerting rules in a single Kibana space could retrieve alerting rule execution telemetry that belongs to spaces the user is not authorized to access. The disclosed telemetry includes rule identifiers, rule names, space identifiers, execution outcomes, timestamps, and execution counters.
AI Analysis
Technical Summary
This vulnerability (CVE-2026-72650) in Elastic Kibana involves an authorization bypass through a user-controlled key (CWE-639). An authenticated user authorized to read alerting rules in a single Kibana space can retrieve alerting rule execution telemetry belonging to other spaces without proper access control enforcement. The leaked telemetry data includes sensitive metadata such as rule identifiers, rule names, space identifiers, execution outcomes, timestamps, and execution counters. The issue affects Kibana versions 8.0.0 and 9.0.0. There is no vendor advisory or patch available at this time, and no known exploits in the wild have been reported.
Potential Impact
An attacker with legitimate read access to alerting rules in one Kibana space can gain unauthorized visibility into alerting telemetry data from other spaces. This leads to information disclosure of alerting rule metadata and execution details that should be restricted, potentially aiding further reconnaissance or targeted attacks. The impact is limited to confidentiality as there is no integrity or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict user permissions to the minimum necessary and monitor for unusual access patterns. No official remediation or temporary fix has been published by Elastic.
CVE-2026-72650: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Description
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user who is authorized to read alerting rules in a single Kibana space could retrieve alerting rule execution telemetry that belongs to spaces the user is not authorized to access. The disclosed telemetry includes rule identifiers, rule names, space identifiers, execution outcomes, timestamps, and execution counters.
CVSS v3.1
Score 4.3medium
Affected software
pkg:github/elastic/kibanaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability (CVE-2026-72650) in Elastic Kibana involves an authorization bypass through a user-controlled key (CWE-639). An authenticated user authorized to read alerting rules in a single Kibana space can retrieve alerting rule execution telemetry belonging to other spaces without proper access control enforcement. The leaked telemetry data includes sensitive metadata such as rule identifiers, rule names, space identifiers, execution outcomes, timestamps, and execution counters. The issue affects Kibana versions 8.0.0 and 9.0.0. There is no vendor advisory or patch available at this time, and no known exploits in the wild have been reported.
Potential Impact
An attacker with legitimate read access to alerting rules in one Kibana space can gain unauthorized visibility into alerting telemetry data from other spaces. This leads to information disclosure of alerting rule metadata and execution details that should be restricted, potentially aiding further reconnaissance or targeted attacks. The impact is limited to confidentiality as there is no integrity or availability impact reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict user permissions to the minimum necessary and monitor for unusual access patterns. No official remediation or temporary fix has been published by Elastic.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:38.893Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a81bf8831d539b182d7
Added to database: 08/13/2026, 19:26:57 UTC
Last enriched: 08/13/2026, 19:58:36 UTC
Last updated: 08/13/2026, 22:21:21 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.