RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation
Published 17 Sept 2026 · Updated 1 Oct 2026
Is your project on an affected github.com/rabbitmq/amqp091-go?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.13.0
- Fixed in
- 1.13.0
go get github.com/rabbitmq/amqp091-go@v1.13.0Details
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.
Is GHSA-r9c8-gcjp-xfwh in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/rabbitmq/amqp091-go, and gives you the command that fixes it.
More advisories for github.com/rabbitmq/amqp091-go
- LowCVE-2026-107386Pre-negotiation frame limit is not enforced to 4KB in github.com/rabbitmq/amqp091-go · 19 Oct 2026
- MediumCVE-2026-107386amqp091-go: Pre-negotiation frame limit is not enforced to 4KB · 8 Oct 2026
- LowCVE-2026-77407RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields in github.com/rabbitmq/amqp091-go · 1 Oct 2026
- LowCVE-2026-77405RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser in github.com/rabbitmq/amqp091-go · 1 Oct 2026
- LowCVE-2026-77404RabbitMQ amqp091-go: Connection Configuration Overwrite via Unsanitized TLS Path Parameter Injection in github.com/rabbitmq/amqp091-go · 1 Oct 2026
- LowCVE-2026-77412RabbitMQ amqp091-go: Denial of Service via Malicious Field Length in AMQP Client in github.com/rabbitmq/amqp091-go · 1 Oct 2026
References
- Linkgithub.com/rabbitmq/amqp091-go/security/advisories/GHSA-r9c8-gcjp-xfwh
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-77410
- Linkgithub.com/rabbitmq/amqp091-go/pull/346
- Linkgithub.com/rabbitmq/amqp091-go/commit/91b65fa0096a99a580cf51a31b24028ff1c60382
- Packagegithub.com/rabbitmq/amqp091-go
- Linkgithub.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.