Is CVE-2026-77411 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-77411 being exploited in the wild.

How severe is CVE-2026-77411?

Critical severity, with a CVSS score of 4, published 16 September 2026.

Is there a fix for CVE-2026-77411?

Yes. github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-77411 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-77411?

Check whether you run github.com/rabbitmq/amqp091-go (Go) or RabbitMQ Amqp091-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-77411: RabbitMQ amqp091-go protocol desynchronization via integer overflow

CVE-2026-77411 · Severity: critical · CVSS 4 · Published 2026-09-16

RabbitMQ's AMQP protocol client library has a critical flaw in how it parses network messages. When a maliciously crafted message contains an oversized length value, the parser silently fails but leaves unread data in the stream, causing all subsequent messages to become misaligned. An attacker on the network can exploit this to inject fake commands, hijack connections, or potentially execute remote code.

Technologies: github.com/rabbitmq/amqp091-go (Go), RabbitMQ Amqp091-Go. Vendors: Go, RabbitMQ.

Quick answers

Is CVE-2026-77411 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-77411 being exploited in the wild.
How severe is CVE-2026-77411?: Critical severity, with a CVSS score of 4, published 16 September 2026.
Which products and versions are affected?: github.com/rabbitmq/amqp091-go (Go) < 1.13.0, SEMVER:introduced=0,fixed=1.13.0; RabbitMQ Amqp091-Go <UNKNOWN>.
Is there a fix for CVE-2026-77411?: Yes. github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-77411 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-77411?: Check whether you run github.com/rabbitmq/amqp091-go (Go) or RabbitMQ Amqp091-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/rabbitmq/amqp091-go (Go): upgrade to 1.13.0 or later
```
go get github.com/rabbitmq/amqp091-go@v1.13.0
```

Technical details

The vulnerability is a protocol desynchronization bug in the readLongstr function within the amqp091-go library's wire-protocol parser. When parsing a long string field within an AMQP table, a length value exceeding 2^31-1 (0x7FFFFFFF) triggers an integer overflow check that silently returns without consuming the specified bytes from the network buffer. This leaves the parser state misaligned: subsequent read operations interpret arbitrary bytes from the attacker-controlled payload as valid AMQP frame headers, allowing injection of forged protocol commands. The vulnerability requires network access to the AMQP server and affects any client or server using this library. Exploitation can result in frame injection, command hijacking, or remote code execution.

Affected products

RabbitMQ amqp091-go <UNKNOWN>

Identifiers

CVE-2026-77411
GHSA-c5pq-fr2g-9jpf
GO-2026-6496

Timeline

2026-09-17: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.