Answer in brief
CVE-2026-107386 records a Medium severity (CVSS 6.3) vulnerability in amqp091-go: Pre-negotiation frame limit is not enforced to 4KB. The current sources do not mark it as known exploited. The current feed maps rabbitmq/amqp091-go (generic), github.com/rabbitmq/amqp091-go (go), github.com/rabbitmq/amqp091-go (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps rabbitmq/amqp091-go (generic), github.com/rabbitmq/amqp091-go (go), github.com/rabbitmq/amqp091-go (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| rabbitmq/amqp091-gogeneric | >=1.13.0 <1.14.0 | 1.14.0 |
| github.com/rabbitmq/amqp091-gogo | <1.14.0 | 1.14.0 |
| github.com/rabbitmq/amqp091-gogo | >=0 <1.14.0 | 1.14.0 |
Published upstream
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.