CVE-2026-77412: RabbitMQ amqp091-go: Denial of Service via Malicious Field Length in AMQP Client
Summary A vulnerability in the readField function allows a malicious or compromised AMQP server to trigger an unhandled runtime panic in the client application, leading to an immediate crash of the entire process. Details When parsing incoming AMQP frames, the readField function processes byte-array fields (type tag 'x') by reading a 32-bit big-endian integer to determine the length of the data payload.
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 vulnerability in the readField function allows a malicious or compromised AMQP server to trigger an unhandled runtime panic in the client application, leading to an immediate crash of the entire process.
Details When parsing incoming AMQP frames, the readField function processes byte-array fields (type tag 'x') by reading a 32-bit big-endian integer to determine the length of the data payload.
// read.go:253-263
case 'x':
var len int32
if err = binary.Read(r, binary.BigEndian, &len); err != nil {
return nil, err
}
value := make([]byte, len) // PANICS if len < 0If a server transmits a length value of 0xFFFFFFFF, it is interpreted by the client as a signed 32-bit integer with a value of -1. Passing a negative integer to Go's built-in make() function for slice allocation triggers an unrecoverable runtime panic (panic: len out of range).
Because the reader goroutine handles network I/O without an explicit recover() wrapper, this panic propagates up to the runtime root, abruptly terminating the host application.
Attack Vector / Exploitation Scenario An attacker capable of spoofing, compromising, or controlling an AMQP broker can exploit this flaw during two primary phases:
- Connection Establishment: Sending a malicious connection.start handshake frame containing server-properties with an 'x' type field assigned a negative length.
- Message Delivery: Delivering a message payload where the header table contains a malformed field matching the criteria above.
Impact Availability: High. A single malformed frame can reliably crash the client process, resulting in a persistent Denial of Service (DoS) if the client automatically reconnects and receives the same payload.
Credited to suchitd, MirahImage.
References
- https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-4v58-74mf-rjx3
- https://nvd.nist.gov/vuln/detail/CVE-2026-77412
- https://github.com/rabbitmq/amqp091-go/pull/344
- https://github.com/rabbitmq/amqp091-go/commit/669b42bf7b1db76bc6d4973e3634247f680accbf
- https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
- https://github.com/advisories/GHSA-4v58-74mf-rjx3
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
