CVE-2026-72680: Authorization Bypass Through User-Controlled Key in Kibana Agent Builder Leading to Unauthorized Data Modification
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72680?
The severity of CVE-2026-72680 is medium with a score of 6.5.
How does CVE-2026-72680 affect Kibana Agent Builder?
CVE-2026-72680 allows for authorization bypass through user-controlled keys, leading to unauthorized data modification.
How can I fix CVE-2026-72680?
To fix CVE-2026-72680, update to the latest version of Elastic Kibana Agent Builder that addresses this vulnerability.
What types of attacks are possible due to CVE-2026-72680?
CVE-2026-72680 can be exploited by an authenticated user to modify conversations that do not belong to them.
What should I do if I am a user of Kibana Agent Builder regarding CVE-2026-72680?
If you are a user of Kibana Agent Builder, you should evaluate whether your application is vulnerable and apply the recommended updates.