Overview 19 matches · 7 in Waratek scope · 2 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
19matches
7in Waratek scope36.8%
2protected10.5%
1exploited5.3%
0CISA KEV0.0%
2public PoC10.5%
1EPSS ≥ 0.55.3%
Protected by Waratek
2
10.5%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
5
26.3%
Outside Waratek scope
0
0.0%
Not applicable
12
63.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
2
10.5%
partly blocked
0
0.0%
not blocked
17
89.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
5.3%
Working exploit published
1
5.3%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
17
89.5%
split by
peak 9 / year
20141
No exploit published1
Medium1
not blocked1
No public exploit1
20152
Protected by Waratek2
Medium2
blocked by ARMR today2
Exploited1
Working exploit published1
20160
20179
No exploit published2
Not applicable7
High4
Medium5
not blocked9
No public exploit9
20180
20190
20202
No exploit published2
Medium2
not blocked2
No public exploit2
20210
20220
20230
20240
20253
Not applicable3
Medium3
not blocked3
No public exploit3
20262
Not applicable2
High1
Medium1
not blocked2
No public exploit2
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-26933 | Medium | 2026-03-19 | Not applicable | No public exploit | Improper Validation of Array Index (CWE-129) in multiple protocol parser components in Packetbeat can lead Denial of Service via Input Data Manipulation (CAPEC-153). An attacker with the ability to send specially crafted, malformed network packets to a monitored network interface can trigger out-of-bounds read operations, resulting in application crashes or resource exhaustion. This requires the attacker to be positioned on the same network segment as the Packetbeat deployment or to control traffic routed to monitored interfaces. |
| CVE-2026-26932 | High | 2026-02-26 | Not applicable | No public exploit | Improper Validation of Array Index (CWE-129) in the PostgreSQL protocol parser in Packetbeat can lead Denial of Service via Input Data Manipulation (CAPEC-153). An attacker can send a specially crafted packet causing a Go runtime panic that terminates the Packetbeat process. This vulnerability requires the pgsql protocol to be explicitly enabled and configured to monitor traffic on the targeted port. |
| CVE-2025-68388 | Medium | 2025-12-18 | Not applicable | No public exploit | Allocation of resources without limits or throttling (CWE-770) allows an unauthenticated remote attacker to cause excessive allocation (CAPEC-130) of memory and CPU via the integration of malicious IPv4 fragments, leading to a degradation in Packetbeat. |
| CVE-2025-68382 | Medium | 2025-12-18 | Not applicable | No public exploit | Out-of-bounds read (CWE-125) allows an unauthenticated remote attacker to perform a buffer overflow (CAPEC-100) via the NFS protocol dissector, leading to a denial-of-service (DoS) through a reliable process crash when handling truncated XDR-encoded RPC messages. |
| CVE-2025-68381 | Medium | 2025-12-18 | Not applicable | No public exploit | Improper Bounds Check (CWE-787) in Packetbeat can allow a remote unauthenticated attacker to exploit a Buffer Overflow (CAPEC-100) and reliably crash the application or cause significant resource exhaustion via a single crafted UDP packet with an invalid fragment sequence number. |
| CVE-2020-7017 | Medium | 2020-07-27 | No exploit published | No public exploit | In Kibana versions before 6.8.11 and 7.8.1 the region map visualization in contains a stored XSS flaw. An attacker who is able to edit or create a region map visualization could obtain sensitive information or perform destructive actions on behalf of Kibana users who view the region map visualization. |
| CVE-2020-7016 | Medium | 2020-07-27 | No exploit published | No public exploit | Kibana versions before 6.8.11 and 7.8.1 contain a denial of service (DoS) flaw in Timelion. An attacker can construct a URL that when viewed by a Kibana user can lead to the Kibana process consuming large amounts of CPU and becoming unresponsive. |
| CVE-2017-11480 | High | 2017-12-08 | Not applicable | No public exploit | Packetbeat versions prior to 5.6.4 are affected by a denial of service flaw in the PostgreSQL protocol handler. If Packetbeat is listening for PostgreSQL traffic and a user is able to send arbitrary network traffic to the monitored port, the attacker could prevent Packetbeat from properly logging other PostgreSQL traffic. |
| CVE-2017-8444 | Medium | 2017-09-29 | Not applicable | No public exploit | The client-forwarder in Elastic Cloud Enterprise versions prior to 1.0.2 do not properly encrypt traffic to ZooKeeper. If an attacker is able to man in the middle (MITM) the traffic between the client-forwarder and ZooKeeper they could potentially obtain sensitive data. |
| CVE-2017-11479 | Medium | 2017-09-29 | Not applicable | No public exploit | Kibana versions prior to 5.6.1 had a cross-site scripting (XSS) vulnerability in Timelion that could allow an attacker to obtain sensitive information from or perform destructive actions on behalf of other Kibana users. |
| CVE-2017-14730 | High | 2017-09-25 | Not applicable | No public exploit | The init script in the Gentoo app-admin/logstash-bin package before 5.5.3 and 5.6.x before 5.6.1 has "chown -R" calls for user-writable directory trees, which allows local users to gain privileges by leveraging access to a $LS_USER account for creation of a hard link. |
| CVE-2017-8446 | Medium | 2017-08-18 | No exploit published | No public exploit | The Reporting feature in X-Pack in versions prior to 5.5.2 and standalone Reporting plugin versions versions prior to 2.4.6 had an impersonation vulnerability. A user with the reporting_user role could execute a report with the permissions of another reporting user, possibly gaining access to sensitive data. |
| CVE-2015-5619 | Medium | 2017-08-09 | Not applicable | No public exploit | Logstash 1.4.x before 1.4.5 and 1.5.x before 1.5.4 with Lumberjack output or the Logstash forwarder does not validate SSL/TLS certificates from the Logstash server, which might allow attackers to obtain sensitive information via a man-in-the-middle attack. |
| CVE-2015-4165 | High | 2017-08-09 | No exploit published | No public exploit | The snapshot API in Elasticsearch before 1.6.0 when another application exists on the system that can read Lucene files and execute code from them, is accessible by the attacker, and the Java VM on which Elasticsearch is running can write to a location that the other application can read and execute from, allows remote authenticated users to write to and create arbitrary snapshot metadata files, and potentially execute arbitrary code. |
| CVE-2015-5378 | High | 2017-06-27 | Not applicable | No public exploit | Logstash 1.5.x before 1.5.3 and 1.4.x before 1.4.4 allows remote attackers to read communications between Logstash Forwarder agent and Logstash server. |
| CVE-2016-10362 | Medium | 2017-06-16 | Not applicable | No public exploit | Prior to Logstash version 5.0.1, Elasticsearch Output plugin when updating connections after sniffing, would log to file HTTP basic auth credentials. |
| CVE-2015-5531 | Medium | 2015-08-17 | Protected by Waratek | Exploited | Directory traversal vulnerability in Elasticsearch before 1.6.1 allows remote attackers to read arbitrary files via unspecified vectors related to snapshot API calls. |
| CVE-2015-3337 | Medium | 2015-05-01 | Protected by Waratek | Working exploit published | Directory traversal vulnerability in Elasticsearch before 1.4.5 and 1.5.x before 1.5.2, when a site plugin is enabled, allows remote attackers to read arbitrary files via unspecified vectors. |
| CVE-2014-6439 | Medium | 2014-10-10 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in the CORS functionality in Elasticsearch before 1.4.0.Beta1 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. |