CVE-2026-77411

CRITICALPre-NVD 9.59.5
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.5 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 — Patch released this week

Also known asEUVD-2026-80821 (ENISA EUVD) · GHSA-c5pq-fr2g-9jpf (GitHub Security Advisories)Source: ENISA EUVD

9.5EG
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: 9.5Exploit: 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, readLongstr in read.go returns an empty string and a nil error when a declared AMQP longstr length exceeds 0x7FFFFFFF instead of returning ErrSyntax. The function leaves the declared field bytes unread, while readTable treats the operation as successful and continues parsing from the wrong offset. A malicious or compromised broker can provide an oversized longstr in a table field and desynchronize subsequent AMQP parsing, causing attacker-controlled trailing bytes to be interpreted as later fields or frames and disrupting connection integrity and availability. This issue is fixed in version 1.13.0.

CVSS v3
9.5
EG Score
9.5CRITICALmedium confidence
EG Risk
43
EG Risk 43/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)
Severity95% × 45%
Impact severity (EG Severity): CVSS 9.5 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
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 (9.5): severity, escalated by confirmed exploitation. This CVE's 9.5 is its impact severity (EG Severity), not escalated.

EG Severity
9.5 CRITICALCVSS-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-11-01). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 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 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 23, 2026

Advisory Details (4)

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

Protocol Desynchronization and Frame Injection via Integer Overflow in readLongstr · Advisory · rabbitmq/amqp091-go · GitHub

https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-c5pq-fr2g-9jpf
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

Return error when longstring too long.

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

https://github.com/rabbitmq/amqp091-go/pull/347
GitHub commit Patch Available

commit 143c1ace5fa7 (rabbitmq/amqp091-go)

Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 143c1ace5fa7)

https://github.com/rabbitmq/amqp091-go/commit/143c1ace5fa7344cee135e5c7d22970f0de68282

Vendor Advisories for CVE-2026-77411(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17928654872026-10-29redhat
redhatopentelemetry-collector-contrib-main-0.162.0-0.1.hum12026-09-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(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-77411?
CVE-2026-77411 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, readLongstr in read.go returns an empty string and a nil error when a declared AMQP longstr length exceeds 0x7FFFFFFF instead of returning ErrSyntax. The function leaves the declared field bytes unread, while readTable treats the…
When was the CVE record for CVE-2026-77411 published?
The CVE record for CVE-2026-77411 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-77411 actively exploited?
CVE-2026-77411 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-77411?
CVE-2026-77411 has a CVSS base score of 9.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77411?
A fix for CVE-2026-77411 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-77411 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-77411

Explore →

Is Your Infrastructure Affected by CVE-2026-77411?

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

Book a Demo →Browse All CVEs