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.
CVE-2026-77411
CRITICALPre-NVD 9.59.5—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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.5EG
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.5Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.5
- EG Score
- 9.5(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity95% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (4)
Auto-updated Sep 17, 2026Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available
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-9jpfgithub_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
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/347github_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/143c1ace5fa7344cee135e5c7d22970f0de68282Vendor Advisories for CVE-2026-77411(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 19:27 UTCEG score recompute
- 2026-09-18 21:30 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 23:44 UTCEG score recompute
- 2026-09-16 19:25 UTCEG score recompute
- 2026-09-16 18:41 UTCEG score recompute
- 2026-09-16 15:20 UTCEG score recompute
- 2026-09-16 14:51 UTCEG score recompute
- 2026-09-16 14:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-754
Frequently asked(5)
What is CVE-2026-77411?
CVE-2026-77411 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, 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 CVE-2026-77411 disclosed?
CVE-2026-77411 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-77411 actively exploited?
CVE-2026-77411 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 64.9% of all scored CVEs.
What is the CVSS score of CVE-2026-77411?
CVE-2026-77411 has a CVSS v3 base score of 9.5 (NVD).
How do I remediate CVE-2026-77411?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77411, 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
Explore the affected products and dependency analysis for CVE-2026-77411
Is Your Infrastructure Affected by CVE-2026-77411?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.