CVE-2026-77409

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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-80822 (ENISA EUVD)Source: ENISA EUVD

8.2EG
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.5%CVSS: 8.2Exploit: 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, Channel.dispatch in channel.go, confirms.confirm in confirms.go, and Connection.dispatch0 in connection.go synchronously send publisher confirmations, flow-control events, consumer cancellations, returned messages, including NotifyConfirm events and connection block notifications, to application-provided channels. If a listener channel is unbuffered, full, or not drained promptly, the sole reader goroutine blocks and stops processing frames, acknowledgments, deliveries, and heartbeats. Broker-driven event bursts can therefore cause connection stalls, missed heartbeats, deadlocks, and disconnection. This issue is fixed in version 1.13.0.

CVSS
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 partial (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.5%
EPSS %ILE
44th
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 (8.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-08). 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: 14 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 partial (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)14 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 partial (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 Sep 16, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
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 commit Patch Available

commit 5b0ccbb8d7bc (rabbitmq/amqp091-go)

Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 5b0ccbb8d7bc)

https://github.com/rabbitmq/amqp091-go/commit/5b0ccbb8d7bc3dfa18129d9b0f9256d656809494
GitHub pull request Patch Available

Avoid notifications blocking reader.

Patch available: rabbitmq/amqp091-go v1.13.0 (PR #349 merged 2026-06-16)

https://github.com/rabbitmq/amqp091-go/pull/349
GitHub advisoryMentions a patch (unverified)

Denial of Service via Synchronous Event Channel Blocking · Advisory · rabbitmq/amqp091-go · GitHub

https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-wxx3-cj7g-w73j

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel8:17914624282026-10-08redhat
redhatquay/quay-rhel8:17913145142026-10-08redhat
redhatquay/quay-rhel8:17908084432026-10-07redhat
redhatopentelemetry-collector-contrib-main-0.161.0-0.1.hum12026-09-16redhat

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

(3 across 3 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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 146 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 46 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-77409?
CVE-2026-77409 is a high-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, Channel.dispatch in channel.go, confirms.confirm in confirms.go, and Connection.dispatch0 in connection.go synchronously send publisher confirmations, flow-control events, consumer cancellations, returned messages, including…
When was the CVE record for CVE-2026-77409 published?
The CVE record for CVE-2026-77409 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-77409 actively exploited?
CVE-2026-77409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77409?
CVE-2026-77409 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77409?
A fix for CVE-2026-77409 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77409 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-77409

Explore →

Is Your Infrastructure Affected by CVE-2026-77409?

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