CVE-2026-77403

HIGHPre-NVD 8.98.9
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.9 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
Trending — 4 sources updated this week

Also known asEUVD-2026-80807 (ENISA EUVD) · GHSA-xwwf-m8fg-p9q2 (GitHub Security Advisories)Source: ENISA EUVD

8.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.9Exploit: 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, Connection.openTune in connection.go accepts a server-advertised FrameMax below the AMQP frameMinSize value of 4096 bytes because the connection negotiation loop does not enforce the protocol minimum. A malicious or compromised AMQP broker can therefore advertise an extremely small FrameMax, causing later client publications to be fragmented into excessive numbers of frames and write operations. This can consume CPU and stall the client or its host. This issue is fixed in version 1.13.0.

CVSS v3
8.9
EG Score
8.9HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity89% × 45%
Impact severity (EG Severity): CVSS 8.9 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
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.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is its impact severity (EG Severity), not escalated.

EG Severity
8.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 23, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
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 2e0a919b89f3 (rabbitmq/amqp091-go)

Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 2e0a919b89f3)

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

fix: enforce AMQP minimum frame size during negotiation

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

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

Denial of Service via Sub-Spec Frame Size Negotiation · Advisory · rabbitmq/amqp091-go · GitHub

https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-xwwf-m8fg-p9q2

Vendor Advisories for CVE-2026-77403(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

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
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(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 70× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 100 of 125 refreshes 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 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-77403?
CVE-2026-77403 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, Connection.openTune in connection.go accepts a server-advertised FrameMax below the AMQP frameMinSize value of 4096 bytes because the connection negotiation loop does not enforce the protocol minimum. A malicious or compromised AMQP…
When was the CVE record for CVE-2026-77403 published?
The CVE record for CVE-2026-77403 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 23, 2026; the record at its source may have been updated since.
Is CVE-2026-77403 actively exploited?
CVE-2026-77403 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-77403?
CVE-2026-77403 has a CVSS base score of 8.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77403?
A fix for CVE-2026-77403 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77403 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-77403

Explore →

Is Your Infrastructure Affected by CVE-2026-77403?

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

Book a Demo →Browse All CVEs