Skip to content

Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments

High severity GitHub Reviewed Published Dec 19, 2025 to the GitHub Advisory Database • Updated Dec 20, 2025

Package

gomod github.com/elastic/beats (Go)

Affected versions

>= 8.6.0, < 8.19.9
>= 9.0.0, < 9.1.9
>= 9.2.0, < 9.2.3

Patched versions

8.19.9
9.1.9
9.2.3
gomod github.com/elastic/beats/v7 (Go)
< 7.0.0-alpha2.0.20251209162832-28cfc80d2f4e
7.0.0-alpha2.0.20251209162832-28cfc80d2f4e

Description

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 denial-of-service in Packetbeat.

References

Published by the National Vulnerability Database Dec 18, 2025
Published to the GitHub Advisory Database Dec 19, 2025
Reviewed Dec 20, 2025
Last updated Dec 20, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(23rd percentile)

Weaknesses

Allocation of Resources Without Limits or Throttling

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. Learn more on MITRE.

CVE ID

CVE-2025-68388

GHSA ID

GHSA-fj69-23m4-ccvv

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.