Is github.com/elastic/beats affected by CVE-2025-68388?

Go github.com/elastic/beats is affected in >=0.

Is CVE-2025-68388 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.3%.

medium

CVE-2025-68388

Go · github.com/elastic/beats • Go · github.com/elastic/beats/v7

Summary

Elasticsearch Packetbeat has Excessive Allocation of Memory and CPU via Malicious IPv4 Fragments in github.com/elastic/beats

Severity: medium
EPSS: 0.3% (p22)
Also known as: GHSA-fj69-23m4-ccvv, GHSA-fj69-23m4-ccvv#github.com/elastic/beats, GHSA-fj69-23m4-ccvv#github.com/elastic/beats/v7, GO-2025-4253, GO-2025-4253#github.com/elastic/beats, GO-2025-4253#github.com/elastic/beats/v7
Published: 2026-01-23

References

Related advisories

CVE-2026-26931 — medium · Go/github.com/elastic/beats
CVE-2026-26933 — medium · Go/github.com/elastic/beats
CVE-2026-0528 — medium · Go/github.com/elastic/beats
CVE-2025-68383 — medium · Go/github.com/elastic/beats

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.