CVE-2026-77406: RabbitMQ amqp091-go: Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration
Summary A logic and resource exhaustion vulnerability exists in the AMQP client's Quality of Service (Qos) configuration method. The Qos function accepts signed integers (int) for the prefetchCount and prefetchSize parameters but casts them directly to unsigned integers (uint16 and uint32, respectively) when formatting the wire-level frame.
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 logic and resource exhaustion vulnerability exists in the AMQP client's Quality of Service (Qos) configuration method. The Qos function accepts signed integers (int) for the prefetchCount and prefetchSize parameters but casts them directly to unsigned integers (uint16 and uint32, respectively) when formatting the wire-level frame.
If a developer passes a negative integer (such as -1) to these parameters—frequently intended as a sentinel value meaning "no change" or "no limit"—the application performs an implicit signed-to-unsigned conversion. This wraps the values to their absolute maximum limit ($65535$ and $4294967295$). Consequently, a consumer expecting restricted message delivery rates is suddenly flooded with an unlimited volume of messages, potentially exhausting memory resources and crashing the application.
---
Vulnerability Details
Mechanism
The bug manifests during the structural assignment inside the channel's Qos method:
// channel.go:795-796
PrefetchCount: uint16(prefetchCount), // -1 wraps to 65535
PrefetchSize: uint32(prefetchSize), // -1 wraps to 4294967295In Go, converting a negative signed integer to an unsigned integer shifts the value via two's complement arithmetic. Because no boundary validation or signedness check occurs prior to the cast:
- Passing
-1forprefetchCountyields a wire value of65535. - Passing
-1forprefetchSizeyields a wire value of4294967295.
Impact
The AMQP broker interprets a prefetch-count of 65535 as an instruction to dispatch messages to the consumer with virtually no concurrency limits.
If the application is processing heavy payloads or relies on strict rate-limiting to maintain stability, this unexpected flood will cause rapid heap memory growth, unmanageable processing queues, and an eventual Out-Of-Memory (OOM) termination.
---
Attack Vector
An attacker who can manipulate configuration files, environmental variables, or API inputs that dictate client Qos settings can trigger an application-layer Denial of Service:
- Malicious Input: An attacker sets a service's prefetch configuration parameter to
-1. - Implicit Overflow: The application initializes the channel, executes
Qos(-1, ...), and transmits an unintended maximum-capacity request to the RabbitMQ/AMQP broker. - Consumer Exhaustion: The broker flushes the entire contents of the queue directly into the client consumer's network buffer, bypassing expected application concurrency barriers and inducing a crash.
Credited to suchitd.
References
- https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-rm6m-hrcw-jw33
- https://nvd.nist.gov/vuln/detail/CVE-2026-77406
- https://github.com/rabbitmq/amqp091-go/pull/351
- https://github.com/rabbitmq/amqp091-go/commit/3b879e1d1d25b544e26b3bc3d7db3213203c0f3b
- https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
- https://github.com/advisories/GHSA-rm6m-hrcw-jw33
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-77407
RabbitMQ amqp091-go: Plaintext Credential Exposure via Exported PLAIN Authentication Struct Fields
high7.0Sep 17, 2026CVE-2026-77408
RabbitMQ amqp091-go: Silent Data Truncation and State Corruption via Shortstr Integer Overflow
critical9.1Sep 17, 2026
