CVE Vulnerability Catalog

Elasticsearch does not validate a size value from user input before using it to reserve memory for an internal data structure. An authenticated user with read-only privileges can send a single crafted request causing an excessively large allocation. Memory exhaustion raises a fatal error that terminates the node process, causing denial of service and degrading cluster health.

Kibana contains a Relative Path Traversal (CWE-23) vulnerability that can lead to unauthorized deletion of Kibana resources. Kibana Fleet accepted a user-supplied identifier for a Fleet Server host configuration without rejecting relative traversal sequences. The identifier is stored and later incorporated into the request when that configuration is removed.

Fleet Server has a code injection vulnerability (CWE-94) that can lead to execution of attacker-supplied script content. Kibana accepts an identifier for an output configuration without restricting safe characters. The identifier is later placed into a server-side script, so embedded script syntax becomes part of the executed script.

Kibana contains a Missing Authorization (CWE-862) vulnerability that can lead to cross-space information disclosure and unauthorized data modification. Kibana Machine Learning carries out its Elasticsearch operations with elevated internal permissions and relies on a per-request space filter to keep ML data separated. Part of the ML functionality did not apply that filter, so operations from one space were carried out against ML data of every space.

Kibana has a resource allocation vulnerability (CWE-770) leading to denial of service via excessive allocation. A user-supplied list of document fields in the Playground for RAG feature is not bounded or de-duplicated before building responses. A single crafted request can make Kibana build a response far larger than the source data, exhausting instance resources.

Kibana has an incorrect authorization vulnerability (CWE-863) allowing unauthorized deletion of Synthetics private locations. Locations can be shared across spaces, and the deletion safeguard only checks monitors visible in the user's own space. An authenticated user with Synthetics write privilege in one space can delete a location that other spaces depend on, even without access to those spaces.

The Elastic Security capability that suggests existing field values while a user authors endpoint policy artifacts queries Elastic Defend event data with Kibana's internal Elasticsearch account instead of the requesting user's account. Only Kibana feature privileges are verified, not the caller's Elasticsearch index privileges. An authenticated user with Elastic Security feature privileges but no read access to Elastic Defend event indices can retrieve field values, including process command line arguments, which commonly contain tokens, credentials, and other sensitive operational detail.

A Kibana Machine Learning capability that removes a saved object from the current space accepts trained models as a target, but only verifies privileges for anomaly detection and data frame analytics jobs. A user with those job creation privileges but without trained model privilege can remove a trained model from a space. The model is not deleted and remains in other spaces, and the change can be reversed by a privileged user.

A lower privileged user who holds only the privilege to read agent policies can read the entire configuration of a configured Fleet proxy. This would normally require the Fleet privilege to read settings. The proxy configuration possibly contains proxy authentication credentials and private key material that they should not be authorized to view.

The state that Kibana stores for an Observability Onboarding flow is not bound to the user who created the flow, and the routes that read and update that state do not verify ownership. An authenticated user with only generic read access to the space can discover other users' onboarding flows, read their state, and write arbitrary progress data. A tampered flow can also cause the owner's onboarding view to fail with a server error.

Kibana has a resource allocation vulnerability (CWE-770) leading to denial of service via excessive allocation. A specially crafted request from an authenticated user with minimal privileges to a validation capability in the Observability log analysis feature causes unbounded concurrent work. This can exhaust memory and make Kibana unavailable until restart.

Kibana has an authorization bypass vulnerability through user-controlled key (CWE-639), allowing unauthorized query execution against Elastic Agents assigned to a space the user has no access to. A user authorized to run Osquery live queries in one space can have queries executed on hosts in another space, leading to information disclosure to the Osquery results data stream.

Missing Authorization in Kibana can lead to unauthorized execution of Osquery and Elastic Defend response actions on managed hosts. A Kibana user who can author and evaluate Elastic Security detection rules can trigger response actions on enrolled agents without the required privileges.

Kibana has a missing authorization vulnerability (CWE-862) allowing unauthorized execution of Elastic Defend response actions on managed hosts. A user with only detection rule authoring privileges can associate automated endpoint response actions with a rule, even without dedicated endpoint privileges. When the rule generates alerts, the actions are executed on matching hosts.

Kibana has an inefficient algorithmic complexity vulnerability (CWE-407) leading to denial of service via input data manipulation. A specially crafted, deeply nested expression submitted to a TSVB visualization is evaluated with worst-case cost growing disproportionately with input size. Because evaluation runs synchronously, a single request consumes the request-processing thread indefinitely, and Kibana stops responding until restart.

Kibana has a missing authorization vulnerability (CWE-862) leading to information disclosure. An internal data retrieval capability used by Elastic Defend response actions did not enforce Security Solution and endpoint privileges, and retrieved data with elevated internal permissions. An authenticated low-privileged user with no Security Solution, endpoint, or Elasticsearch privileges could read endpoint response action records and response content from managed hosts.

An uncaught exception in Kibana, resulting from improper input validation, can lead to denial of service. An authenticated user with low privileges can submit specially crafted data that causes an internal error and terminates the Kibana process. Kibana becomes unavailable to all users until the service is restarted, and the condition can be triggered repeatedly.

Unbounded resource allocation in Kibana can lead to denial of service. An authenticated user with low privileges can submit a specially crafted malformed payload to a visualization feature, causing uncontrolled memory growth. The Kibana process is terminated once memory is exhausted, and the service becomes unavailable until restart.

Cross-Site Request Forgery in Kibana can lead to privilege escalation. A user allowed to create visualizations can save a crafted Vega visualization that, when opened by another user, triggers authenticated requests in the victim's session.

Authorization bypass through user-controlled key in Fleet Server can lead to information disclosure. The authorization decision for artifact downloads relied on a client-supplied value that was not validated against the server-side record of the agent's assignment. An authenticated party with valid agent credentials could retrieve a policy the agent is not assigned to.