Vulnerabilities

Kibana contains an incorrect authorization flaw (CWE-863) in which Elasticsearch cluster privilege declarations supplied by integration packages are not validated before being used to mint credentials for enrolled Elastic Agents. A user who holds Fleet management privileges can manipulate these privilege declarations (CAPEC-153, input data manipulation) so that every Elastic Agent assigned to a targeted policy receives a credential with arbitrarily elevated Elasticsearch cluster privileges, potentially up to full cluster administration. An attacker with this level of access gains high confidentiality and integrity impact (CVSS 3.1: 8.1, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N), since the mis-issued agent credentials can be used to access or modify cluster data broadly. Affected users are organizations running Elastic Kibana with Fleet management and enrolled Elastic Agents that use integration packages; specific affected and patched version ranges are not provided in the available data. There is currently no known exploitation: the flaw is not in CISA KEV, no public proof-of-concept is known, and EPSS estimates only a 0.2% probability of exploitation within 30 days.

Do: Upgrade Kibana to a patched release per Elastic's advisory (specific fixed versions are not stated in the available data). Restrict Fleet management privileges to trusted users, and review integration packages for overly broad Elasticsearch cluster privilege declarations. Audit credentials issued to enrolled Elastic Agents for unexpected cluster privileges and re-issue/rotate agent credentials if abuse is suspected.

Incorrect Authorization (CWE-863) in Elastic Cloud on Kubernetes (ECK) can lead to unauthorized modification of data via Metadata Spoofing (CAPEC-690). An actor holding limited Kubernetes permissions confined to a single namespace could cause attacker-controlled certificate material to be included in the Elasticsearch client trust bundle managed by ECK in a separate namespace.

Elastic Agent on Windows, when installed in unprivileged mode, creates resources used by the agent service with access-control permissions broader than required (CWE-732, incorrect permission assignment for critical resource). A local attacker with low privileges can exploit this by replacing the agent service's binaries (CAPEC-642), causing the service to execute attacker-chosen code. Because the agent service runs in a privileged context, this results in full SYSTEM-level privileges on the affected Windows host. Only Windows systems where Elastic Agent was installed in unprivileged mode are affected, per the vendor description. There is currently no known public proof-of-concept, the issue is not in CISA's KEV, and EPSS estimates only about a 0.1% probability of exploitation in the next 30 days.

Do: Inventory Windows endpoints running Elastic Agent and identify which were installed in unprivileged mode, as those are the affected hosts. Upgrade those agents to the patched release cited in Elastic's security advisory (Elastic is the CNA; check elastic.co/security for the exact fixed version). As an interim mitigation, verify and restrict ACLs on the Elastic Agent installation directory and service resources so unprivileged users cannot write to or replace the service binaries.

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) in Elastic Maps Server can lead to information disclosure via Path Traversal (CAPEC-126). An unauthenticated attacker able to reach the service over the network could cause it to return the contents of files outside its intended content directory that are readable by the server process.

Kibana's Fleet feature contains a path traversal flaw (CWE-22, CAPEC-126) that lets an attacker direct administrative actions at unintended internal resources. It is triggered when a low-privileged user holding Fleet Settings write access supplies a malicious pathname, and an administrator subsequently interacts with the affected Fleet interface, causing that administrative action to execute against the wrong targets. The attacker gains deletion of privileged resources such as user accounts and other organizational assets, with high integrity and availability impact but no confidentiality impact per the CVSS 3.1 vector (7.3, AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H). Any Elastic Kibana deployment with the Fleet feature enabled, where non-administrative users have Fleet Settings write permissions, is potentially affected; exploitation additionally requires an administrator to interact with the Fleet UI. There is currently no known exploitation, no public proof-of-concept, the flaw is not in CISA KEV, and EPSS estimates a 0.3% probability of exploitation within 30 days.

Do: Upgrade Kibana to a patched release per Elastic's advisory for CVE-2026-78590, since exact fixed version numbers are not included in the available data. Until patched, restrict Fleet Settings write permissions to trusted administrators and review Fleet audit logs for unexpected deletions of users or other privileged resources. Administrators should verify Fleet prompts and resource paths before acting on them.

Improper Handling of Highly Compressed Data (CWE-409) in APM Server can lead to a persistent denial of service via Excessive Allocation (CAPEC-130). An authenticated user with write access to source map content could store specially crafted, highly compressed content that exhausts the memory available to APM Server when it is later processed, terminating the process. The condition recurs on every restart until the stored content is removed.

Allocation of Resources Without Limits or Throttling (CWE-770) in Filebeat can lead to a denial of service via Excessive Allocation (CAPEC-130). An attacker able to reach the Filebeat HTTP ingestion endpoint could send specially crafted compressed requests that exhaust the memory resources of the Filebeat process.

Incorrect Authorization (CWE-863) in Fleet Server can lead to a denial of service of agent upload operations via Privilege Abuse (CAPEC-122). Fleet Server does not correctly verify session ownership during multi-part data upload operations, allowing any authenticated agent to interfere with the active upload sessions belonging to other enrolled agents.

Elastic Kibana contains an incorrect authorization flaw (CWE-863) that permits privilege escalation through scheduled workflow executions. A user holding workflow edit permissions can manipulate a workflow so that its scheduled runs execute with the privileges of a different, higher-privileged user instead of their own context. The attacker thereby gains the ability to access and modify data beyond their authorized scope; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, score 8.3) indicates network-based exploitation requiring only low privileges and no user interaction. Any Kibana deployment in which users have been granted workflow edit permissions is plausibly affected, though the specific affected version ranges are not stated in the available data. No public proof-of-concept, KEV listing, or known in-the-wild exploitation exists, and EPSS currently puts the 30-day exploitation probability at 0.4%.

Do: Restrict the workflow edit privilege to trusted administrators and review your Kibana role definitions to see which users currently hold it. Watch for Elastic's advisory on CVE-2026-63137 and upgrade Kibana to the patched release it specifies. Audit recent scheduled workflow executions for runs that occurred under unexpected or higher-privileged user contexts.

Elasticsearch's machine learning component (CVE-2026-72649) contains a deserialization-of-untrusted-data flaw (CWE-502) that can lead to remote code execution via object injection. An attacker who is an authenticated user with sufficient privileges to create and deploy trained models can submit a specially crafted trained model artifact, causing attacker-controlled logic to execute with a materially broader system-call surface than intended. Successful exploitation yields remote code execution with high impact to confidentiality, integrity, and availability (CVSS 3.1: 8.8 High, network vector, low privileges required, no user interaction). Only Elasticsearch deployments where the machine learning feature is in use and model-creation/deployment privileges are granted to untrusted or compromised accounts are meaningfully exposed. As of this analysis there is no known public proof-of-concept, the issue is not in CISA's Known Exploited Vulnerabilities catalog, and no in-the-wild exploitation has been reported; EPSS currently estimates roughly a 0.6% probability of exploitation within 30 days.

Do: Inventory your Elasticsearch clusters for use of the machine learning feature and review which users hold privileges to create and deploy trained models, restricting them to trusted operators and, ideally, trusted model sources. Apply the patched Elasticsearch release identified in Elastic's security advisory as soon as it is available, prioritizing ML-enabled clusters (particularly security/SIEM deployments). Until patched, treat trained-model artifact uploads as untrusted input and monitor model-creation and deployment activity for anomalies.

Winlogbeat's Windows installer placed runtime files in a directory writable by unprivileged users, creating an improper link-resolution issue (CWE-59). A low-privileged attacker who already has access to the host can pre-position malicious filesystem links so that a subsequent elevated Winlogbeat operation writes to or deletes arbitrary files. Successful exploitation results in denial of service, with high integrity and availability impact but no confidentiality impact per the CVSS 3.1 score of 7.1. Organizations running Winlogbeat on Windows hosts installed via the Windows installer are affected. No public proof-of-concept is known, the flaw is not in CISA KEV, and EPSS estimates the 30-day exploitation probability at about 0.1%.

Do: Consult Elastic's security advisory for CVE-2024-14047 to identify the affected Windows installer versions and upgrade Winlogbeat to a fixed release. In the interim, check that the Winlogbeat installation directory and its runtime files are not writable by unprivileged users and restrict local access on hosts running it, watching for unexpected file deletions.

Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to unauthorized data modification via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). Under certain conditions, an authenticated user could reference another user's AI Assistant conversation identifier to access or modify a conversation they do not own. Successful exploitation requires knowledge of a hard-to-guess identifier.

A flaw in Elasticsearch allows a low-privileged authenticated user to submit a single request containing a crafted user-supplied input. A specific internal component validates the input using a recursive routine and applies no bound to the length of the value being validated, so the validation causes the thread to exhaust its stack. The resulting fatal error is not handled by the surrounding execution paths and terminates the affected node process, producing a denial of service.

Improper Control of Generation of Code ('Code Injection') (CWE-94) in Fleet Server can lead to the execution of attacker-supplied script content via Code Injection (CAPEC-242). Kibana accepted an identifier for an output configuration without restricting it to safe characters. That identifier is later placed into a server-side script that Fleet Server builds as part of routine agent policy processing, so script syntax embedded in the identifier became part of the script that was executed rather than being treated as data.