Overview 21 matches · 1 in Waratek scope · 1 protected · 3 exploited · 2 CISA KEV · 3 public PoC · 3 EPSS ≥ 0.5
21matches
1in Waratek scope4.8%
1protected4.8%
3exploited14.3%
2CISA KEV9.5%
3public PoC14.3%
3EPSS ≥ 0.514.3%
Protected by Waratek
1
4.8%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
20
95.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
4.8%
partly blocked
0
0.0%
not blocked
20
95.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
3
14.3%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
18
85.7%
split by
peak 4 / year
20151
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
20160
20170
20184
Not applicable4
Critical4
not blocked4
Exploited1
No public exploit3
20193
Not applicable3
Critical3
not blocked3
Exploited1
No public exploit2
20200
20210
20220
20233
Not applicable3
Critical3
not blocked3
No public exploit3
20244
Not applicable4
Critical4
not blocked4
No public exploit4
20254
Not applicable4
Critical4
not blocked4
No public exploit4
20262
Not applicable2
Critical2
not blocked2
No public exploit2
201520162017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-72676 | Critical | 2026-08-13 | Not applicable | No public exploit | 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. |
| CVE-2026-33466 | Critical | 2026-04-08 | Not applicable | No public exploit | Improper Limitation of a Pathname to a Restricted Directory (CWE-22) in Logstash can lead to arbitrary file write and potentially remote code execution via Relative Path Traversal (CAPEC-139). The archive extraction utilities used by Logstash do not properly validate file paths within compressed archives. An attacker who can serve a specially crafted archive to Logstash through a compromised or attacker-controlled update endpoint can write arbitrary files to the host filesystem with the privileges of the Logstash process. In certain configurations where automatic pipeline reloading is enabled, this can be escalated to remote code execution. |
| CVE-2025-37729 | Critical | 2025-10-13 | Not applicable | No public exploit | Improper neutralization of special elements used in a template engine in Elastic Cloud Enterprise (ECE) can lead to a malicious actor with Admin access exfiltrating sensitive information and issuing commands via a specially crafted string where Jinjava variables are evaluated. |
| CVE-2025-25014 | Critical | 2025-05-06 | Not applicable | No public exploit | A Prototype pollution vulnerability in Kibana leads to arbitrary code execution via crafted HTTP requests to machine learning and reporting endpoints. |
| CVE-2024-12556 | Critical | 2025-04-08 | Not applicable | No public exploit | Prototype Pollution in Kibana can lead to code injection via unrestricted file upload combined with path traversal. |
| CVE-2025-25015 | Critical | 2025-03-05 | Not applicable | No public exploit | Prototype pollution in Kibana leads to arbitrary code execution via a crafted file upload and specifically crafted HTTP requests. In Kibana versions >= 8.15.0 and < 8.17.1, this is exploitable by users with the Viewer role. In Kibana versions 8.17.1 and 8.17.2 , this is only exploitable by users that have roles that contain all the following privileges: fleet-all, integrations-all, actions:execute-advanced-connectors |
| CVE-2024-37285 | Critical | 2024-11-14 | Not applicable | No public exploit | A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. A successful attack requires a malicious user to have a combination of both specific Elasticsearch indices privileges https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv and Kibana privileges https://www.elastic.co/guide/en/fleet/current/fleet-roles-and-privileges.html assigned to them. The following Elasticsearch indices permissions are required * write privilege on the system indices .kibana_ingest* * The allow_restricted_indices flag is set to true Any of the following Kibana privileges are additionally required * Under Fleet the All privilege is granted * Under Integration the Read or All privilege is granted * Access to the fleet-setup privilege is gained through the Fleet Server’s service account token |
| CVE-2024-37288 | Critical | 2024-09-09 | Not applicable | No public exploit | A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. This issue only affects users that use Elastic Security’s built-in AI tools https://www.elastic.co/guide/en/security/current/ai-for-security.html and have configured an Amazon Bedrock connector https://www.elastic.co/guide/en/security/current/assistant-connect-to-bedrock.html . |
| CVE-2024-37287 | Critical | 2024-08-13 | Not applicable | No public exploit | A flaw allowing arbitrary code execution was discovered in Kibana. An attacker with access to ML and Alerting connector features, as well as write access to internal ML indices can trigger a prototype pollution vulnerability, ultimately leading to arbitrary code execution. |
| CVE-2024-37282 | Critical | 2024-06-28 | Not applicable | No public exploit | It was identified that under certain specific preconditions, an API key that was originally created with a specific privileges could be subsequently used to create new API keys that have elevated privileges. |
| CVE-2023-46668 | Critical | 2023-10-26 | Not applicable | No public exploit | If Elastic Endpoint (v7.9.0 - v8.10.3) is configured to use a non-default option in which the logging level is explicitly set to debug, and when Elastic Agent is simultaneously configured to collect and send those logs to Elasticsearch, then Elastic Agent API keys can be viewed in Elasticsearch in plaintext. These API keys could be used to write arbitrary data and read Elastic Endpoint user artifacts. |
| CVE-2023-31422 | Critical | 2023-10-26 | Not applicable | No public exploit | An issue was discovered by Elastic whereby sensitive information is recorded in Kibana logs in the event of an error. The issue impacts only Kibana version 8.10.0 when logging in the JSON layout or when the pattern layout is configured to log the %meta pattern. Elastic has released Kibana 8.10.1 which resolves this issue. The error object recorded in the log contains request information, which can include sensitive data, such as authentication credentials, cookies, authorization headers, query params, request paths, and other metadata. Some examples of sensitive data which can be included in the logs are account credentials for kibana_system, kibana-metricbeat, or Kibana end-users. |
| CVE-2023-31415 | Critical | 2023-05-04 | Not applicable | No public exploit | Kibana version 8.7.0 contains an arbitrary code execution flaw. An attacker with All privileges to the Uptime/Synthetics feature could send a request that will attempt to execute JavaScript code. This could lead to the attacker executing arbitrary commands on the host system with permissions of the Kibana process. |
| CVE-2019-7612 | Critical | 2019-03-25 | Not applicable | No public exploit | A sensitive data disclosure flaw was found in the way Logstash versions before 5.6.15 and 6.6.1 logs malformed URLs. If a malformed URL is specified as part of the Logstash configuration, the credentials for the URL could be inadvertently logged as part of the error message. |
| CVE-2019-7610 | Critical | 2019-03-25 | Not applicable | No public exploit | Kibana versions before 6.6.1 contain an arbitrary code execution flaw in the security audit logger. If a Kibana instance has the setting xpack.security.audit.enabled set to true, an attacker could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system. |
| CVE-2019-7609 | Critical | 2019-03-25 | Not applicable | Exploited | Kibana versions before 5.6.15 and 6.6.1 contain an arbitrary code execution flaw in the Timelion visualizer. An attacker with access to the Timelion application could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system. |
| CVE-2018-17246 | Critical | 2018-12-20 | Not applicable | Exploited | Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the Console plugin. An attacker with access to the Kibana Console API could send a request that will attempt to execute javascript code. This could possibly lead to an attacker executing arbitrary commands with permissions of the Kibana process on the host system. |
| CVE-2018-17245 | Critical | 2018-12-20 | Not applicable | No public exploit | Kibana versions 4.0 to 4.6, 5.0 to 5.6.12, and 6.0 to 6.4.2 contain an error in the way authorization credentials are used when generating PDF reports. If a report requests external resources plaintext credentials are included in the HTTP request that could be recovered by an external resource provider. |
| CVE-2018-3822 | Critical | 2018-03-30 | Not applicable | No public exploit | X-Pack Security versions 6.2.0, 6.2.1, and 6.2.2 are vulnerable to a user impersonation attack via incorrect XML canonicalization and DOM traversal. An attacker might have been able to impersonate a legitimate user if the SAML Identity Provider allows for self registration with arbitrary identifiers and the attacker can register an account which an identifier that shares a suffix with a legitimate account. Both of those conditions must be true in order to exploit this flaw. |
| CVE-2015-5377 | Critical | 2018-03-06 | Not applicable | No public exploit | Elasticsearch before 1.6.1 allows remote attackers to execute arbitrary code via unspecified vectors involving the transport protocol. NOTE: ZDI appears to claim that CVE-2015-3253 and CVE-2015-5377 are the same vulnerability |
| CVE-2015-1427 | Critical | 2015-02-17 | Protected by Waratek | Exploited | The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script. |