CVE-2026-77405

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-80818 (ENISA EUVD) · GHSA-33mj-cw25-m34h (GitHub Security Advisories) · GO-2026-6492 (OSV.dev)Source: ENISA EUVD

9.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
57
EG Risk 57/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Oct 2, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

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-m34h
GitHub release Patch Available

v1.13.0

Patch available: rabbitmq/amqp091-go v1.13.0

https://github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0
GitHub pull request 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/355
GitHub 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/c9fd433ecac2e557919e51acc9d809390c402c6e

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17930027922026-11-05redhat
redhatrhacm2/acm-grafana-rhel9:17928654872026-10-29redhat
gogithub.com/rabbitmq/amqp091-go @ 1.13.0 (fixes < 1.13.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-rabbitmq-amqp091-go1.10.0-1 ... 1.9.0-1 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-rabbitmq-amqp091-go1.10.0-1, 1.11.0-1, 1.12.0-1, 1.14.0-1, 1.15.0-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-github-rabbitmq-amqp091-go1.10.0-1, 1.11.0-1, 1.12.0-1
  • every version up to 1.14.0-1: fixed in 1.14.0-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/rabbitmq/amqp091-go—
  • every version up to 1.13.0: fixed in 1.13.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 277 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 177 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-12 18:49 UTCEchelonGraph re-scored
  3. 2026-11-12 18:49 UTCVendor advisory
  4. 2026-11-12 18:49 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  5. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-11 16:34 UTCEchelonGraph re-scored
  8. 2026-11-11 16:34 UTCVendor advisory
  9. 2026-11-11 16:34 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  10. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-11-10 14:19 UTCEchelonGraph re-scored
  12. 2026-11-10 14:19 UTCVendor advisory
  13. 2026-11-10 14:19 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  14. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-11-09 12:05 UTCEchelonGraph re-scored
  16. 2026-11-09 12:05 UTCVendor advisory
  17. 2026-11-09 12:05 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  18. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-11-08 09:50 UTCEchelonGraph re-scored
  20. 2026-11-08 09:50 UTCVendor advisory
  21. 2026-11-08 09:50 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  22. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  23. 2026-11-07 07:36 UTCEchelonGraph re-scored
  24. 2026-11-07 07:36 UTCVendor advisory
  25. 2026-11-07 07:36 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
Show 75 more
  1. 2026-11-06 18:25 UTCOSV refresh
  2. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-11-06 05:22 UTCEchelonGraph re-scored
  4. 2026-11-06 05:22 UTCVendor advisory
  5. 2026-11-06 05:22 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  6. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-05 03:08 UTCEchelonGraph re-scored
  8. 2026-11-05 03:08 UTCVendor advisory
  9. 2026-11-05 03:08 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  10. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-11-04 00:54 UTCEchelonGraph re-scored
  12. 2026-11-04 00:54 UTCVendor advisory
  13. 2026-11-04 00:54 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  14. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-11-02 22:40 UTCEchelonGraph re-scored
  16. 2026-11-02 22:40 UTCVendor advisory
  17. 2026-11-02 22:40 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  18. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  19. 2026-11-01 20:16 UTCEchelonGraph re-scored
  20. 2026-11-01 20:16 UTCVendor advisory
  21. 2026-11-01 20:16 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  22. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-33mj-cw25-m34h · GitHub severity CRITICAL
  23. 2026-10-31 18:03 UTCEchelonGraph re-scored
  24. 2026-10-31 18:03 UTCVendor advisory
  25. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  26. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  27. 2026-10-30 15:48 UTCEchelonGraph re-scored
  28. 2026-10-30 15:48 UTCVendor advisory
  29. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-10-29 13:35 UTCEchelonGraph re-scored
  31. 2026-10-29 13:35 UTCVendor advisory
  32. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  33. 2026-10-28 11:21 UTCEchelonGraph re-scored
  34. 2026-10-28 11:21 UTCVendor advisory
  35. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  36. 2026-10-27 08:41 UTCEchelonGraph re-scored
  37. 2026-10-27 08:41 UTCVendor advisory
  38. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  39. 2026-10-26 04:28 UTCEchelonGraph re-scored
  40. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  41. 2026-10-25 14:01 UTCEchelonGraph re-scored
  42. 2026-10-25 02:11 UTCEchelonGraph re-scored
  43. 2026-10-25 02:11 UTCVendor advisory
  44. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  45. 2026-10-23 23:58 UTCEchelonGraph re-scored
  46. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  47. 2026-10-22 21:44 UTCEchelonGraph re-scored
  48. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-10-21 19:29 UTCEchelonGraph re-scored
  50. 2026-10-21 19:29 UTCVendor advisory
  51. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  52. 2026-10-20 17:15 UTCEchelonGraph re-scored
  53. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  55. 2026-10-19 15:00 UTCEchelonGraph re-scored
  56. 2026-10-19 15:00 UTCVendor advisory
  57. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-10-18 12:46 UTCVendor advisory
  59. 2026-10-18 03:12 UTCEchelonGraph re-scored
  60. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-10-17 10:32 UTCEchelonGraph re-scored
  62. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  63. 2026-10-16 08:16 UTCEchelonGraph re-scored
  64. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-10-15 06:01 UTCEchelonGraph re-scored
  66. 2026-10-15 06:01 UTCVendor advisory
  67. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  68. 2026-10-14 01:39 UTCEchelonGraph re-scored
  69. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  70. 2026-10-12 21:50 UTCEchelonGraph re-scored
  71. 2026-10-12 21:50 UTCVendor advisory
  72. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  73. 2026-10-12 15:37 UTCEchelonGraph re-scored
  74. 2026-10-11 23:06 UTCVendor advisory
  75. 2026-10-11 19:23 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-77405?
CVE-2026-77405 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-77405 published?
The CVE record for CVE-2026-77405 was published on September 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-77405 actively exploited?
CVE-2026-77405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77405?
CVE-2026-77405 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77405?
A fix for CVE-2026-77405 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77405 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77405

Explore →

Is Your Infrastructure Affected by CVE-2026-77405?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.