CVE-2026-77405: RabbitMQ amqp091-go Missing Explicit TLS Minimum Version Vulnerability

CRITICAL
Advisory Identifier: GHSA-33mj-cw25-m34h
CWE-326 CWE-316
Published
Advisory Summary

CVE-2026-77405 is a CRITICAL missing explicit tls minimum version vulnerability (CWE-326: Inadequate Encryption Strength) affecting RabbitMQ amqp091-go libraries in the Go ecosystem. The issue involves missing explicit tls minimum version configuration in uri parser. Remediation is available by upgrading affected packages to version 1.13.0.

CVE-2026-77405 at a Glance

CVE Identifier CVE-2026-77405
GHSA Identifier GHSA-33mj-cw25-m34h
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-326: Inadequate Encryption Strength
Affected Product RabbitMQ amqp091-go
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-77405

To remediate this vulnerability, upgrade all affected RabbitMQ amqp091-go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rabbitmq/amqp091-go fixed: 1.13.0
Upgrade github.com/rabbitmq/amqp091-go to 1.13.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rabbitmq/amqp091-go

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-77405, inspect your project dependencies for RabbitMQ amqp091-go:

inspect dependencies for github.com/rabbitmq/amqp091-go

Analyze the terminal output to locate any version of RabbitMQ amqp091-go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.13.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-326: Inadequate Encryption Strength, where the product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required. In RabbitMQ amqp091-go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A structural security weakness exists in the AMQP client's TLS configuration generator (`tlsConfigFromURI`). When constructing a `*tls.Config` object from an `amqps://` connection URI, the library initializes the structure without explicitly defining the `MinVersion` field. While modern versions of the Go compiler toolchain (Go 1.18+) default the implicit minimum version to TLS 1.2, this security posture relies entirely on an implicit toolchain dependency. If the library is compiled using legacy Go toolchains (Go < 1.18), or if a future toolchain introduces fallback behavior, the client could silently negotiate obsolete and insecure TLS 1.0 or TLS 1.1 protocols during connection handshakes with a compromised or malicious AMQP broker. --- ## Vulnerability Details ### Mechanism The vulnerability lies in the lack of an explicit safety floor when assigning configurations inside the URI component: ```go // Example within uri.go's tlsConfigFromURI cfg := &tls.Config{ ServerName: host, // MinVersion is left completely unassigned (defaults to 0, or toolchain default) } ``` In the Go standard library (`crypto/tls`), leaving `MinVersion: 0` instructs the runtime to choose the toolchain's default minimum. Prior to Go 1.18, this default allowed negotiation down to TLS 1.0. Relying on implicit compiler configurations violates secure coding practices by decoupling the library's security posture from its source code, leaving applications vulnerable based solely on how they are built. ### Impact If a client application is built with a legacy compiler environment or a custom Go runtime, an attacker capable of executing a Man-in-the-Middle (MitM) attack can force the connection to downgrade to TLS 1.0 or 1.1. This exposes the AMQP protocol data stream to well-known cryptographic vulnerabilities (such as BEAST, POODLE, or SWEET32), allowing the attacker to decrypt or alter message payloads, connection parameters, and authentication credentials. --- ## Attack Vector An attacker performing a network-level downgrade attack can intercept a client connection built under a legacy toolchain: 1. **Interception:** A client application compiled on a legacy pipeline attempts to establish an encrypted connection to an AMQP broker. 2. **Protocol Downgrade:** The attacker intercepts the TLS Client Hello handshake and forces a downgrade negotiation to TLS 1.0. 3. **Cryptographic Exploitation:** Because `MinVersion` was never explicitly locked to `tls.VersionTLS12` by the library, the client accepts the weak cipher suites, allowing the attacker to monitor or manipulate the underlying AMQP session data.

CVE-2026-77405 Affected RabbitMQ amqp091-go Versions

1 component(s)
Fixed Versions:
1.13.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rabbitmq/amqp091-go
Go
< 1.13.0
1.13.0

References

Frequently Asked Questions

What is CVE-2026-77405?
CVE-2026-77405 is a security vulnerability in RabbitMQ amqp091-go involving Missing Explicit TLS Minimum Version Configuration In URI Parser under CWE-326: Inadequate Encryption Strength.
Which RabbitMQ amqp091-go versions are affected?
Affected versions include releases prior to 1.13.0 across affected packages: github.com/rabbitmq/amqp091-go.
What version fixes CVE-2026-77405?
Upgrading to 1.13.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rabbitmq/amqp091-go affected?
Yes, github.com/rabbitmq/amqp091-go is affected in releases prior to 1.13.0. Upgrade your dependency to 1.13.0 or later.
What CWE is associated with CVE-2026-77405?
CVE-2026-77405 is classified under CWE-326: Inadequate Encryption Strength (The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.).
How can I check Go dependencies for CVE-2026-77405?
Run the dependency tree command: 'inspect dependencies for github.com/rabbitmq/amqp091-go'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-33mj-cw25-m34h",
  "modified" : "2026-09-17T17:04:01Z",
  "published" : "2026-09-17T17:04:01Z",
  "aliases" : [ "CVE-2026-77405" ],
  "summary" : "RabbitMQ amqp091-go: Missing Explicit TLS Minimum Version Configuration In URI Parser",
  "details" : "## Summary\nA structural security weakness exists in the AMQP client's TLS configuration generator (`tlsConfigFromURI`). When constructing a `*tls.Config` object from an `amqps://` connection URI, the library initializes the structure without explicitly defining the `MinVersion` field. \n\nWhile modern versions of the Go compiler toolchain (Go 1.18+) default the implicit minimum version to TLS 1.2, this security posture relies entirely on an implicit toolchain dependency. If the library is compiled using legacy Go toolchains (Go < 1.18), or if a future toolchain introduces fallback behavior, the client could silently negotiate obsolete and insecure TLS 1.0 or TLS 1.1 protocols during connection handshakes with a compromised or malicious AMQP broker.\n\n---\n\n## Vulnerability Details\n\n### Mechanism\nThe vulnerability lies in the lack of an explicit safety floor when assigning configurations inside the URI component:\n\n```go\n// Example within uri.go's tlsConfigFromURI\ncfg := &tls.Config{\n    ServerName: host,\n    // MinVersion is left completely unassigned (defaults to 0, or toolchain default)\n}\n```\n\nIn the Go standard library (`crypto/tls`), leaving `MinVersion: 0` instructs the runtime to choose the toolchain's default minimum. Prior to Go 1.18, this default allowed negotiation down to TLS 1.0. Relying on implicit compiler configurations violates secure coding practices by decoupling the library's security posture from its source code, leaving applications vulnerable based solely on how they are built.\n\n### Impact\nIf a client application is built with a legacy compiler environment or a custom Go runtime, an attacker capable of executing a Man-in-the-Middle (MitM) attack can force the connection to downgrade to TLS 1.0 or 1.1. This exposes the AMQP protocol data stream to well-known cryptographic vulnerabilities (such as BEAST, POODLE, or SWEET32), allowing the attacker to decrypt or alter message payloads, connection parameters, and authentication credentials.\n\n---\n\n## Attack Vector\nAn attacker performing a network-level downgrade attack can intercept a client connection built under a legacy toolchain:\n\n1. **Interception:** A client application compiled on a legacy pipeline attempts to establish an encrypted connection to an AMQP broker.\n2. **Protocol Downgrade:** The attacker intercepts the TLS Client Hello handshake and forces a downgrade negotiation to TLS 1.0.\n3. **Cryptographic Exploitation:** Because `MinVersion` was never explicitly locked to `tls.VersionTLS12` by the library, the client accepts the weak cipher suites, allowing the attacker to monitor or manipulate the underlying AMQP session data.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:L/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rabbitmq/amqp091-go"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.13.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-33mj-cw25-m34h"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-77405"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/pull/355"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/commit/c9fd433ecac2e557919e51acc9d809390c402c6e"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rabbitmq/amqp091-go"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-316", "CWE-326" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T17:04:01Z",
    "nvd_published_at" : "2026-09-16T15:17:47Z"
  }
}