CVE-2026-77410: RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation
Summary A flaw in the recvContent function allows a malicious AMQP server to trigger an Out-of-Memory (OOM) error, forcing the host operating system or container runtime to immediately terminate the client process. Vulnerability Details When receiving message content payloads, the client processes the expected size from the content header framework.
Published Sep 17, 2026
Affected packages
github.com/rabbitmq/amqp091-go
- Ecosystem
- Go
- Affected
- < 1.13.0
- Fixed in
- 1.13.0
- Check
go list -m github.com/rabbitmq/amqp091-go
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary A flaw in the recvContent function allows a malicious AMQP server to trigger an Out-of-Memory (OOM) error, forcing the host operating system or container runtime to immediately terminate the client process.
Vulnerability Details When receiving message content payloads, the client processes the expected size from the content header framework. The recvContent function attempts to optimize performance by pre-allocating memory for the message body based on the ch.header.Size field, which is a 64-bit unsigned integer (uint64).
// channel.go:495-496
if cap(ch.body) == 0 {
ch.body = make([]byte, 0, ch.header.Size) // unbounded
}The underlying library fails to validate or cap this requested size against any upper boundary—such as the maximum frame size negotiated during connection establishment (FrameMax). If a server specifies an extreme body size (e.g., 2^62 bytes), the Go runtime attempts to allocate an exabyte-scale slice capacity. This immediately exhausts available system memory, causing the operating system's OOM killer to terminate the application.
Attack Vector / Exploitation Scenario
- Message Delivery Phase: A malicious or compromised AMQP broker sends a standard
basic.deliverframe containing a content header with an intentionally inflatedbody-sizevariable. - Authentication Requirement: No special privileges or authentication bypasses are required; the crash occurs seamlessly during normal message consumption.
Impact
- Availability: High. Exploded memory consumption results in an instant process termination, destroying application state and availability for all threads sharing the environment.
Credited to suchitd, MirahImage.
References
- https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh
- https://nvd.nist.gov/vuln/detail/CVE-2026-77410
- https://github.com/rabbitmq/amqp091-go/pull/346
- https://github.com/rabbitmq/amqp091-go/commit/91b65fa0096a99a580cf51a31b24028ff1c60382
- https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
- https://github.com/advisories/GHSA-r9c8-gcjp-xfwh
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-107386
amqp091-go: Pre-negotiation frame limit is not enforced to 4KB
medium6.3Oct 8, 2026CVE-2026-77403
RabbitMQ amqp091-go: Denial of Service via Sub-Spec Frame Size Negotiation
high8.9Sep 17, 2026CVE-2026-77404
RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection
high8.7Sep 17, 2026CVE-2026-77405
RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser
critical9.4Sep 17, 2026CVE-2026-77406
RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration
high8.2Sep 17, 2026CVE-2026-77407
RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields
high7.0Sep 17, 2026
