CVE-2026-115297: Packetbeat can lead to denial of · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 3 Nov 2026, 19:45 UTC
Thin evidence
One scorer or none| CNA (elastic) | CVSS 3.1 | 6.5 |
|---|
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| ElasticPacketbeat | Affected
| Fixed in– |
AI-suggested
Until a fix is available, limiting network access to the monitored segment or disabling AMQP monitoring in Packetbeat may reduce exposure.
Description
A NULL Pointer Dereference vulnerability (CWE-476) exists in the AMQP protocol parser of Packetbeat. This flaw allows an unauthenticated attacker to cause a denial of service by sending specially crafted AMQP network traffic that triggers a Go runtime panic, terminating the Packetbeat process. Exploitation requires network access to the monitored segment but no AMQP authentication. Packetbeat does not collect telemetry when not running.