Live › vulnerability › CVE-2026-107386
Go to dashboardThe amqp091-go Go client for AMQP 0.9.1 accepts frames before connection tuning is done and does not enforce the 4KB pre-negotiation frame limit, because a zero value is used for both 'not yet negotiated' and 'unlimited'. A malicious or compromised AMQP peer can send a small frame header declaring a huge payload, making the client allocate attacker-chosen memory and possibly crash with out-of-memory before authentication completes.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/rabbitmq/amqp091-go | go | < 1.14.0 | 1.14.0 |
Check whether go.mod or go.sum pins github.com/rabbitmq/amqp091-go below 1.14.0 (e.g. grep amqp091-go go.sum).
Upgrade github.com/rabbitmq/amqp091-go to 1.14.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-107386")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.