CVE-2026-107386
Description
A flaw was found in amqp091-go. A malicious server or remote peer can cause a Denial of Service (DoS) by sending a crafted frame header declaring an excessively large payload size during initial connection setup. This flaw causes the client to allocate large amounts of memory before validating the frame or completing authentication, resulting in memory exhaustion and termination of the client process.
Statement
A flaw was found in the amqp091-go Go AMQP 0.9.1 client library. In version 1.13.0, the frame-size mitigation introduced for a prior allocation vulnerability (GHSA-r9c8-gcjp-xfwh) can be bypassed before connection.tune negotiation completes. This occurs because Connection.maxFrameSize uses a zero value to represent both the "not yet negotiated" and "negotiated unlimited" states, causing the frame-size check to be skipped during the pre-negotiation window. A malicious or compromised AMQP broker, or a man-in-the-middle attacker, can send a crafted body-frame header with a large declared payload length, causing the client to allocate attacker-controlled amounts of memory before authentication completes. This can result in severe memory pressure, out-of-memory termination, or loss of the client process. The vulnerability is only present in version 1.13.0 and is fixed in version 1.14.0.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.9 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
