HighGHSA-6c5v-hqjr-5xxpCVE-2026-79921GO-2026-6372

amqp091-go has a Potential Memory Exhaustion/Protocol Violation via Broker-Controlled Oversized Payload

Published 3 Sept 2026 · Updated 15 Sept 2026

Is your project on an affected github.com/rabbitmq/amqp091-go?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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
Update to the fixed version for your release line, for example:go get github.com/rabbitmq/amqp091-go@v1.13.0

Details

Summary A vulnerability exists in the amqp091-go client library where a compromised or malicious AMQP broker can force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints.

Details During a standard AMQP 0-9-1 connection handshake, the client and the broker negotiate a maximum frame size (frame_max), for example, 4096 bytes.

However, after negotiation, a malicious broker can send a valid basic.deliver sequence containing a content body frame whose header declares a payload size larger than the negotiated frame_max. Instead of enforcing the agreed-upon limit and closing the connection with a frame-error (as mandated by the AMQP 0-9-1 specification), the amqp091-go client:

1. Accepts the broker-declared oversized frame size. 2. Allocates memory based on this oversized declaration. 3. Reads the payload, assembles it into the message, and delivers it to the consumer.

Impact

  • Denial of Service (DoS): If a broker sends extremely large frame sizes, it can trigger significant memory allocations on the client side, potentially leading to Out-Of-Memory (OOM) crashes.
  • Protocol Violation: The client fails to enforce negotiated connection parameters, trusting the broker implicitly even after constraints have been established.

Is GHSA-6c5v-hqjr-5xxp 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
All 21 advisories for github.com/rabbitmq/amqp091-go

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.