CVE-2026-107386

Published: Ott 08, 2026 Last Modified: Ott 09, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 6,3
Attack Vector: network
Attack Complexity: low
Privileges Required: none
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation Available

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.

EPSS (Exploit Prediction Scoring System)

Trend Analysis

EPSS (Exploit Prediction Scoring System)

Prevede la probabilità di sfruttamento basata su intelligence sulle minacce e sulle caratteristiche della vulnerabilità.

EPSS Score
0,0049
Percentile
0,4th
Updated

EPSS Score Trend (Last 3 Days)

770

Allocation of Resources Without Limits or Throttling

Incomplete
Common Consequences
Security Scopes Affected:
Availability
Potential Impacts:
Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Dos: Resource Consumption (Other)
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/rabbitmq/amqp091-go/commit/6723e8cff8710f0a6bf5fb4af375e2850…
https://github.com/rabbitmq/amqp091-go/pull/377
https://github.com/rabbitmq/amqp091-go/releases/tag/v1.14.0
https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-w6r9-248c-frg8