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.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-w6r9-248c-frg8 | amqp091-go: Pre-negotiation frame limit is not enforced to 4KB |
Thu, 08 Oct 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rabbitmq
Rabbitmq amqp091-go |
|
| Vendors & Products |
Rabbitmq
Rabbitmq amqp091-go |
Thu, 08 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | amqp091-go is a Go AMQP 0.9.1 client. From 1.13.0 until 1.14.0, the frame-size mitigation from the prior allocation advisory can be bypassed before connection.tune completes because Connection.maxFrameSize uses zero for both the not-yet-negotiated and negotiated-unlimited states. A malicious or compromised AMQP peer can send a short body-frame header with a large declared payload length, causing ReadFrame and the body-frame parser to allocate attacker-selected memory before the payload is received or the frame's protocol state is rejected. The condition is reachable through public Open even when Config.FrameSize is set to the protocol minimum and can cause severe memory pressure, out-of-memory termination, or loss of the client process before authentication completes. This issue is fixed in version 1.14.0. | |
| Title | amqp091-go: Pre-negotiation frame limit is not enforced to 4KB | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-08T18:54:12.465Z
Reserved: 2026-10-07T21:07:54.988Z
Link: CVE-2026-107386
No data.
Status : Deferred
Published: 2026-10-08T19:17:01.347
Modified: 2026-10-08T21:35:53.890
Link: CVE-2026-107386
No data.
OpenCVE Enrichment
Updated: 2026-10-08T21:00:14Z
-
CWE-770
Allocation of Resources Without Limits or Throttling
Github GHSA