Live › vulnerability › CVE-2026-77410
Go to dashboardThe amqp091-go Go client preallocates a message body buffer using the size declared in an AMQP content header without capping it. A malicious or compromised RabbitMQ broker can declare an enormous body size and make the client process run out of memory and crash.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| github.com/rabbitmq/amqp091-go | go | < 1.13.0 | 1.13.0 |
Run go list -m github.com/rabbitmq/amqp091-go in the project and check whether the version is below 1.13.0.
Upgrade github.com/rabbitmq/amqp091-go to 1.13.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-77410")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.