Quick answers
- Is CVE-2026-77405 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77405 being exploited in the wild.
- How severe is CVE-2026-77405?
- 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.
- Is there a fix for CVE-2026-77405?
- 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-77405 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77405?
- 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 exists in the `tlsConfigFromURI` function in the AMQP client library, which constructs a `*tls.Config` object without explicitly setting the `MinVersion` field. In Go, an unset `MinVersion` defaults to the toolchain's implicit minimum—TLS 1.0 in pre-1.18 versions. An attacker performing a network-level Man-in-the-Middle attack can force protocol downgrade to TLS 1.0 or 1.1, exposing the connection to known cryptographic attacks (BEAST, POODLE, SWEET32). This affects clients compiled with legacy Go versions or non-standard runtimes. The fix requires explicitly configuring `MinVersion: tls.VersionTLS12` in the TLS configuration builder.
Affected products
- RabbitMQ amqp091-go
Identifiers
- CVE-2026-77405
- GHSA-33mj-cw25-m34h
- GO-2026-6492
Timeline
- 2026-09-17: disclosed