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

Medium 6.3 Published Updated

A malicious AMQP peer can cause memory exhaustion and crash the client process by bypassing frame size limits before connection negotiation completes.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-107386?

CVE-2026-107386 is a medium-severity denial of service vulnerability in rabbitmq amqp091-go, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-770

Which versions are affected by CVE-2026-107386?

3 open source packages ship an affected version, including github.com/rabbitmq/amqp091-go.

PackageAffectedFixed in
github.com/rabbitmq/amqp091-go GoAll versions1.14.0
github.com/rabbitmq/amqp091-go GoAll versions1.14.0
github.com/rabbitmq/amqp091-go GoAll versions1.14.0

How do I fix CVE-2026-107386?

Upgrade github.com/rabbitmq/amqp091-go to 1.14.0 or later.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-107386 being exploited?

There is no known exploitation of CVE-2026-107386 in the wild and no public exploit code.

Sources

Also known as CLEANSTART-2026-BX72159, CLEANSTART-2026-VR61817, CLEANSTART-2026-ZB44736, DEBIAN-CVE-2026-107386, ECHO-a87c-d3c1-0535, GHSA-w6r9-248c-frg8 and 26 more.

Is CVE-2026-107386 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free