Description

Kibana Agent Builder does not correctly verify that the requesting user holds the privileges required by a separate Kibana feature before it creates and runs a tool that invokes that feature's functionality. This allows privilege escalation and could lead to disclosure of sensitive information that the user is not authorized to read.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-08-13T20:17:28.853Z",
  "pubdate": "2026-08-13T20:17:28.853Z",
  "executiveSummary": "An authorization bypass vulnerability exists within Kibana Agent Builder, classified as a privilege escalation and sensitive information disclosure flaw.\nThe vulnerability affects Kibana Agent Builder and arises from improper authorization checks when a requesting user interacts with separate Kibana features.\nThe primary impact of successful exploitation includes unauthorized privilege escalation and the potential disclosure of sensitive information that the victim user lacks the explicit permissions to access.\nAn authenticated attacker with lower-privileged access can leverage this flaw to coerce the Agent Builder component into creating and executing tools that invoke high-privilege feature functionality without validating the caller's underlying authorization state.\nThe risk implications are severe, as unauthorized actors can circumvent intended Role-Based Access Control (RBAC) boundaries within the Kibana environment, potentially leading to unauthorized data exposure and administrative capability abuse.\nExploitation requires the attacker to possess authenticated access to Kibana and the ability to interact with the Agent Builder interface, executing malicious or unauthorized tool invocations that bypass secondary feature-level privilege verification.",
  "technicalDetails": "The root cause of the vulnerability resides in a missing authorization check within the Kibana Agent Builder component. Specifically, when the Agent Builder instantiates and executes a tool designed to interface with a separate Kibana feature, it fails to verify whether the requesting user context holds the requisite privileges mandated by that specific target feature.\nThe vulnerable component is the Kibana Agent Builder execution and tool-generation pipeline, which handles the orchestration of feature-invoking mechanisms.\nDuring standard operation, feature interactions should strictly enforce authorization boundaries by validating user roles and permissions against the requested subsystem. However, the Agent Builder acts as an intermediary that bypasses these secondary verification steps, directly invoking underlying functionality upon request.\nThe attack flow proceeds as follows: First, an authenticated low-privileged user interacts with the Kibana Agent Builder interface. Second, the user requests the creation or execution of a tool mapped to a separate, restricted Kibana feature for which they possess no direct authorization. Third, the Agent Builder accepts the request, failing to perform an access control check against the target feature's security requirements. Fourth, the Agent Builder successfully creates and runs the tool, executing the high-privilege functionality on behalf of the user.\nAs a result of this payload behavior, the execution context improperly inherits broader capabilities, enabling unauthorized data access and operations.\nThe post-exploitation impact includes the breach of confidentiality regarding sensitive data managed by restricted Kibana features, alongside unauthorized administrative actions executed through the abused tooling."
}