CVE-2026-77405: CWE-326: Inadequate Encryption Strength in rabbitmq amqp091-go
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, tlsConfigFromURI in uri.go creates tls.Config values without setting MinVersion to tls.VersionTLS12. Builds using a Go runtime whose default permits TLS 1.0 or TLS 1.1 can therefore negotiate an obsolete protocol version when connecting through an amqps URI. A network attacker able to influence TLS negotiation with such a legacy build may weaken transport protection for AMQP messages and credentials. This issue is fixed in version 1.13.0.
AI Analysis
Technical Summary
The RabbitMQ amqp091-go client (a Go implementation of AMQP 0.9.1) versions before 1.13.0 do not set the MinVersion field in tls.Config to tls.VersionTLS12 in the tlsConfigFromURI function. Consequently, when built with a Go runtime that permits TLS 1.0 or TLS 1.1, the client may negotiate these obsolete TLS versions during AMQPS connections. This allows a network attacker capable of influencing TLS negotiation to weaken the transport encryption protecting AMQP messages and credentials. The issue is resolved in version 1.13.0 by enforcing a minimum TLS version of 1.2.
Potential Impact
An attacker with network access who can influence TLS negotiation may cause the client to use weaker TLS protocols (1.0 or 1.1), reducing the confidentiality and integrity of AMQP messages and credentials transmitted over the network. This undermines transport security, potentially exposing sensitive data to interception or tampering.
Mitigation Recommendations
Upgrade to amqp091-go version 1.13.0 or later, where the minimum TLS version is enforced to TLS 1.2, mitigating the risk of negotiating obsolete and insecure TLS versions. No other mitigation is specified.
CVE-2026-77405: CWE-326: Inadequate Encryption Strength in rabbitmq amqp091-go
Description
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, tlsConfigFromURI in uri.go creates tls.Config values without setting MinVersion to tls.VersionTLS12. Builds using a Go runtime whose default permits TLS 1.0 or TLS 1.1 can therefore negotiate an obsolete protocol version when connecting through an amqps URI. A network attacker able to influence TLS negotiation with such a legacy build may weaken transport protection for AMQP messages and credentials. This issue is fixed in version 1.13.0.
CVSS v4.0
Score 9.4critical
Affected software
rabbitmq
amqp091-go
pkg:golang/github.com/rabbitmq/amqp091-goRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The RabbitMQ amqp091-go client (a Go implementation of AMQP 0.9.1) versions before 1.13.0 do not set the MinVersion field in tls.Config to tls.VersionTLS12 in the tlsConfigFromURI function. Consequently, when built with a Go runtime that permits TLS 1.0 or TLS 1.1, the client may negotiate these obsolete TLS versions during AMQPS connections. This allows a network attacker capable of influencing TLS negotiation to weaken the transport encryption protecting AMQP messages and credentials. The issue is resolved in version 1.13.0 by enforcing a minimum TLS version of 1.2.
Potential Impact
An attacker with network access who can influence TLS negotiation may cause the client to use weaker TLS protocols (1.0 or 1.1), reducing the confidentiality and integrity of AMQP messages and credentials transmitted over the network. This undermines transport security, potentially exposing sensitive data to interception or tampering.
Mitigation Recommendations
Upgrade to amqp091-go version 1.13.0 or later, where the minimum TLS version is enforced to TLS 1.2, mitigating the risk of negotiating obsolete and insecure TLS versions. No other mitigation is specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:55:27.023Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aaaabfd55bf5e2cf5bf8d46
Added to database: 09/16/2026, 14:47:25 UTC
Last enriched: 09/16/2026, 15:02:21 UTC
Last updated: 09/16/2026, 23:10:31 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.