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.
Published: 2026-08-13
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The CVE involves the Kibana Agent Builder A2A JSON‑RPC API. An authenticated user with only read privilege can supply a conversation identifier that is already in use by another user. Because the ownership check does not differentiate between a nonexistent conversation and one owned by a different user, the request replaces the targeted conversation and reassigns it to the requesting account. The original owner permanently loses access to the conversation and its message history. The attacker can modify a conversation without reading its content, resulting in loss of integrity and availability for the affected data, but no direct disclosure of confidential information occurs.

Affected Systems

Elastic Kibana. The vulnerability applies to the Agent Builder component of Kibana, and it impacts all users of the same Kibana space where the conversation ID collision can occur. Version information is unknown.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no confirmed widespread exploitation. The attack requires the attacker to be authenticated within Kibana and to have read privileges for the Agent Builder. An attacker can exploit the vulnerability by submitting a crafted request to the JSON‑RPC endpoint, bypassing ownership checks. While exploitation does not allow reading the overwritten conversation, it can cause loss of user data and trust issues for impacted accounts.

Generated by OpenCVE AI on August 13, 2026 at 22:00 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Kibana to a patched release that resolves the ownership check flaw.
  • If an upgrade is not immediately possible, restrict the Agent Builder read privilege to only trusted users or disable the Agent Builder API for all but essential roles.
  • Consider monitoring the API for repeated unauthorized conversation ID submissions and enforce stricter input validation on the conversation identifiers to prevent collisions.

Generated by OpenCVE AI on August 13, 2026 at 22:00 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 03 Sep 2026 19:15:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:elastic:kibana:*:*:*:*:*:*:*:*

Thu, 13 Aug 2026 22:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 13 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Elastic
Elastic kibana
Vendors & Products Elastic
Elastic kibana

Thu, 13 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
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.
Title Authorization Bypass Through User-Controlled Key in Kibana Agent Builder Leading to Unauthorized Data Modification
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: elastic

Published:

Updated: 2026-08-13T20:33:55.775Z

Reserved: 2026-08-10T11:17:58.730Z

Link: CVE-2026-72680

cve-icon Vulnrichment

Updated: 2026-08-13T20:33:52.262Z

cve-icon NVD

Status : Analyzed

Published: 2026-08-13T20:17:28.733

Modified: 2026-09-03T18:59:01.647

Link: CVE-2026-72680

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-13T22:15:03Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key