CVE-2026-107386 · GHSA-w6r9-248c-frg8

amqp091-go: Pre-negotiation frame limit is not enforced to 4KB

Risk score: 51/100
CVSS: 6.3 v4.0
Exploit chance (30 days): 0.5%
Published: 8 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is: 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 c…
Affected: github.com/rabbitmq/amqp091-go (go) < 1.14.0
Fix: Upgrade github.com/rabbitmq/amqp091-go to 1.14.0 or later.
Exploitation: No known exploitation

Why it is Yellow

CVSS 6.3 medium
On your watchlist: Go

Affected packages

Package	Ecosystem	Vulnerable	Fixed in
github.com/rabbitmq/amqp091-go	go	< 1.14.0	1.14.0

References

Original 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.

Last activity 8 Oct 2026. Patch Forecast updates every hour.