CVE-2025-68381 Packetbeat Improper Bounds Check
A remote unauthenticated attacker can crash Packetbeat or exhaust resources by sending a crafted UDP packet with an invalid fragment sequence number.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-68381?
CVE-2025-68381 is a medium-severity memory corruption vulnerability in Elastic Packetbeat, published on 18 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-787
Which versions are affected by CVE-2025-68381?
It affects 1 product.
Products include Elasticsearch Packetbeat.
How do I fix CVE-2025-68381?
No fix has been published for CVE-2025-68381 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-68381 being exploited?
There is no known exploitation of CVE-2025-68381 in the wild and no public exploit code.
Other vulnerabilities in Elastic Packetbeat
- CVE-2017-11480 Denial of Service in Packetbeat
- CVE-2025-68382 Packetbeat Out-of-bounds Read
- CVE-2026-26933 Improper Validation of Array Index in Packetbeat Leading to Denial of Service
- CVE-2026-26932 Improper Validation of Array Index in Packetbeat Leading to Denial of Service
- CVE-2025-68388 Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments
Sources
Also known as GHSA-9gqx-7h84-8hg2.