Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 16 Sep 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0. | |
| Title | RabbitMQ amqp091-go: Resource Exhaustion (OOM) via Unbounded Body Buffer Allocation | |
| Weaknesses | CWE-789 | |
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-16T15:41:15.593Z
Reserved: 2026-08-20T19:55:27.024Z
Link: CVE-2026-77410
No data.
Status : Received
Published: 2026-09-16T15:17:50.430
Modified: 2026-09-16T15:17:50.430
Link: CVE-2026-77410
No data.
OpenCVE Enrichment
No data.
-
CWE-789
Memory Allocation with Excessive Size Value