---
id: "CVE-2026-115297"
kind: "vulnerability"
aliases: ["CVE-2026-115297"]
title: "Packetbeat: crafted AMQP traffic crashes the monitoring agent process"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["amqp", "elastic", "infrastructure", "observability", "packetbeat"]
not_affected_if: ["amqp-not-monitored", "packetbeat-not-deployed"]
published_at: "2026-11-03T17:17:55+00:00"
first_seen_at: "2026-11-03T17:21:55+00:00"
updated_at: "2026-11-03T17:24:16+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115297", "first_seen_at": "2026-11-03T17:21:55+00:00"}]
---

# Packetbeat: crafted AMQP traffic crashes the monitoring agent process

Packetbeat, Elastic's network monitoring agent, has a null pointer dereference in its AMQP protocol parser. A single crafted packet on a monitored network segment makes the Go process panic and exit, stopping network telemetry collection.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Packetbeat version with `packetbeat version`
- Check whether the AMQP protocol is enabled in the Packetbeat configuration file (`packetbeat.yml`) under `packetbeat.protocols`
- Check whether Packetbeat is running on a host that sees AMQP traffic

## Timeline

- 2026-11-03T17:21:55+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-115297

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_