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.
CVE-2026-77405
CRITICALPre-NVD 9.49.4—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.4
- EG Score
- 9.4(medium)
- EG Risk
- 57(Track)EG Risk 57/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity94% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (4)
Auto-updated Sep 17, 2026Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available
Missing Explicit TLS Minimum Version Configuration In URI Parser · Advisory · rabbitmq/amqp091-go · GitHub
https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-33mj-cw25-m34hgithub_release Patch Available
v1.13.0
Patch available: rabbitmq/amqp091-go v1.13.0
https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0github_pr Patch Available
fix: explicitly enforce TLS 1.2 minimum version in tlsConfigFromURI
Patch available: rabbitmq/amqp091-go v1.13.0 (PR #355 merged 2026-06-19)
https://github.com/rabbitmq/amqp091-go/pull/355github_commit Patch Available
commit c9fd433ecac2 (rabbitmq/amqp091-go)
Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit c9fd433ecac2)
https://github.com/rabbitmq/amqp091-go/commit/c9fd433ecac2e557919e51acc9d809390c402c6eVendor Advisories for CVE-2026-77405(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/rabbitmq/amqp091-go | — | 1.13.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 11:08 UTCVendor advisory
- 2026-09-18 22:40 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 18:32 UTCEG score recompute
- 2026-09-18 18:15 UTCEG score recompute
- 2026-09-17 20:23 UTCEG score recompute
- 2026-09-16 15:20 UTCEG score recompute
- 2026-09-16 14:46 UTCEG score recompute
- 2026-09-16 14:45 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-77405?
CVE-2026-77405 is a critical vulnerability published on September 16, 2026. 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…
When was CVE-2026-77405 disclosed?
CVE-2026-77405 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77405 actively exploited?
CVE-2026-77405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.9% of all scored CVEs.
What is the CVSS score of CVE-2026-77405?
CVE-2026-77405 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-77405?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77405, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77405
Is Your Infrastructure Affected by CVE-2026-77405?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.