cve.bz

CVE-2026-77405 rabbitmq amqp091-go: Inadequate Encryption Strength

9.4 criticalEPSS 0.3%Fix available

Critical (9.4) in rabbitmq amqp091-go. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/rabbitmq/amqp091-go 1.13.0.

On this page
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.

Severity

CVSS 4.0

9.4 critical
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
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-09-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-326 Inadequate Encryption Strength
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-77405 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-77405?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-77405?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-77405 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
rabbitmq amqp091-go< 1.13.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-33mj-cw25-m34hGogithub.com/rabbitmq/amqp091-go<1.13.01.13.0
GO-2026-6492Gogithub.com/rabbitmq/amqp091-go<1.13.01.13.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13golang-github-rabbitmq-amqp091-gono fix listedDEBIAN-CVE-2026-77405
Debian14golang-github-rabbitmq-amqp091-go1.14.0-1DEBIAN-CVE-2026-77405
Ubuntu24.04:LTS, 26.04:LTS, 26.10golang-github-rabbitmq-amqp091-gono fix listedUBUNTU-CVE-2026-77405
Azure Linux3kedano fix listedAZL-103182
Azure Linux3telegraf1.31.0-34AZL-103284

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw has an Important impact. Red Hat product streams that ship amqp091-go before 1.13.0 are Affected because tlsConfigFromURI does not set an explicit TLS MinVersion when parsing AMQPS URIs. Exploitation requires a man-in-the-middle position on the path to the AMQP broker; Go 1.18 or later client defaults further raise complexity by preferring TLS 1.2 when MinVersion is unset. Streams that already ship amqp091-go 1.13.0 or later contain the explicit fix and are Not affected. The issue is not Critical because it is not remotely exploitable without those high-complexity prerequisites, and it does not provide unauthenticated remote code execution.

Red Hat's mitigation

Ensure clients are built with Go 1.18 or later so the TLS client default is at least TLS 1.2. Restrict AMQP clients to trusted brokers and limit broker network exposure. If using DialTLS with a custom tls.Config, set MinVersion to tls.VersionTLS12 or higher explicitly.

ProductPackageStateAdvisory
Multicluster Global Hub 1.7.4multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1793002792Fixed 2026-11-05RHSA-2026:95517
Red Hat Advanced Cluster Management for Kubernetes 2.13rhacm2/acm-grafana-rhel9:1792865487Fixed 2026-10-29RHSA-2026:92307
Cryostat 4cryostat/cryostat-storage-rhel9Affected
Custom Metric Autoscaler operator for Red Hat Openshiftcustom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9Not affected
Custom Metric Autoscaler operator for Red Hat Openshiftcustom-metrics-autoscaler/custom-metrics-autoscaler-admission-webhooks-rhel9Not affected
Custom Metric Autoscaler operator for Red Hat Openshiftcustom-metrics-autoscaler/custom-metrics-autoscaler-rhel9Not affected
Custom Metric Autoscaler operator for Red Hat Openshiftcustom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operatorNot affected
OpenShift Serverlessopenshift-serverless-1/kn-plugin-event-sender-rhel9Not affected
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-operator-bundleNot affected
Red Hat Advanced Cluster Management for Kubernetes 2rhacm2/volsync-rhel9Not affected
Red Hat Hardened Imagesopentelemetry-collector-contribNot affected
Red Hat OpenStack Platform 18.0rhoso-operators/rabbitmq-cluster-rhel9-operatorNot affected
Red Hat Quay 3quay/clair-rhel8Not affected
Red Hat Quay 3quay/clair-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-77405.

Attack patterns (CAPEC)

  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-112 Brute Force Severity: High
  • CAPEC-192 Protocol Analysis Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON