Skip to main content
VulnerabilityPublished

CVE-2026-115297: Elastic Packetbeat · NULL Pointer Dereference

Affects Elastic PacketbeatSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 3 Nov 2026, 17:58 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (elastic)CVSS 3.16.5
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ElasticPacketbeatAffected
  • >=8.0.0 <=8.19.23
  • >=9.0.0 <=9.4.8
  • >=9.5.0 <=9.5.5
Fixed in–

AI-suggested

Until a fix is available, restrict network access to Packetbeat monitoring segments to trusted sources to reduce exposure.

Description

NULL Pointer Dereference (CWE-476) in the AMQP protocol parser in Packetbeat can lead to denial of service via specially crafted network traffic. An unauthenticated attacker who can send traffic on a network segment that Packetbeat monitors for AMQP can cause a Go runtime panic that terminates the Packetbeat process. A single crafted packet is sufficient. No AMQP authentication is necessary. While Packetbeat is not running, it does not collect network telemetry.

References

Community reviews

Loading reviews…