Skip to content
Fencer Vulns
medium 5.3

CVE-2025-68388 json

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

published 2025-12-18 10 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-204397 , GHSA-fj69-23m4-ccvv , GO-2025-4253

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/elastic/beats 8.19.9, 9.1.9, 9.2.3
  • go github.com/elastic/beats/v7 7.0.0-alpha2.0.20251209162832-28cfc80d2f4e
  • elasticsearch packetbeat 8.19.9, 9.1.9, 9.2.3
  • elastic beats 7.0.0-alpha2.0.20251209162832-28cfc80d2f4e
  • elasticsearch beats 7.0.0-alpha2.0.20251209162832-28cfc80d2f4e
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260123T022811-150000.1.140.1

suse advisories SUSE-SU-2026:0292-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
10 mo ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/elastic/beats
>=8.6.0, <8.19.9
>=9.0.0, <9.1.9
>=9.2.0, <9.2.3
all versions
8.19.9
9.1.9
9.2.3
go github.com/elastic/beats/v7
<7.0.0-alpha2.0.20251209162832-28cfc80d2f4e
7.0.0-alpha2.0.20251209162832-28cfc80d2f4e

Affected products

  • Elastic Packetbeat

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.