CVE-2026-72680: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Kibana Agent Builder A2A JSON-RPC API endpoint derives the identifier of a stored conversation from a user-supplied input, and the ownership check on that identifier does not distinguish between a conversation that does not exist and one that exists but belongs to another user. As a result, an authenticated user holding only the Agent Builder read privilege can supply an identifier already in use by another user in the same space and cause that user's conversation to be replaced and reassigned to the requesting account. The original owner permanently loses access to the conversation and its history. The impact is limited to loss of integrity and availability of the affected conversation; the attacker does not read the overwritten content.
AI Analysis
Technical Summary
The vulnerability exists because the API endpoint derives the identifier of a stored conversation from user-supplied input and does not properly distinguish between non-existent conversations and those owned by other users. This allows an authenticated user with limited privileges to overwrite another user's conversation by reusing an existing identifier in the same space, causing permanent loss of access for the original owner. The flaw is classified as CWE-639 (Authorization Bypass Through User-Controlled Key).
Potential Impact
The impact is limited to loss of integrity and availability of the affected conversation data. The attacker cannot read the overwritten conversation content, so confidentiality is not affected. The original owner permanently loses access to their conversation and its history, which could disrupt workflows relying on that data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround has been published at this time. Users should monitor Elastic's advisories for updates and consider restricting Agent Builder read privileges until a fix is available.
CVE-2026-72680: CWE-639 Authorization Bypass Through User-Controlled Key in Elastic Kibana
Description
Kibana Agent Builder A2A JSON-RPC API endpoint derives the identifier of a stored conversation from a user-supplied input, and the ownership check on that identifier does not distinguish between a conversation that does not exist and one that exists but belongs to another user. As a result, an authenticated user holding only the Agent Builder read privilege can supply an identifier already in use by another user in the same space and cause that user's conversation to be replaced and reassigned to the requesting account. The original owner permanently loses access to the conversation and its history. The impact is limited to loss of integrity and availability of the affected conversation; the attacker does not read the overwritten content.
CVSS v3.1
Score 6.5medium
Affected software
Run 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
The vulnerability exists because the API endpoint derives the identifier of a stored conversation from user-supplied input and does not properly distinguish between non-existent conversations and those owned by other users. This allows an authenticated user with limited privileges to overwrite another user's conversation by reusing an existing identifier in the same space, causing permanent loss of access for the original owner. The flaw is classified as CWE-639 (Authorization Bypass Through User-Controlled Key).
Potential Impact
The impact is limited to loss of integrity and availability of the affected conversation data. The attacker cannot read the overwritten conversation content, so confidentiality is not affected. The original owner permanently loses access to their conversation and its history, which could disrupt workflows relying on that data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround has been published at this time. Users should monitor Elastic's advisories for updates and consider restricting Agent Builder read privileges until a fix is available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- elastic
- Date Reserved
- 2026-08-10T11:17:58.730Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7e1a85bf8831d539b18419
Added to database: 08/13/2026, 19:27:01 UTC
Last enriched: 08/13/2026, 19:43:25 UTC
Last updated: 08/13/2026, 20:57:21 UTC
Views: 3
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.