RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, readField in read.go reads the length of an AMQP byte-array field with type tag x into a signed int32 and passes the value directly to make when allocating the field buffer. A malicious or compromised broker can encode a value such as 0xFFFFFFFF, which becomes -1 and causes a len out of range runtime panic. The panic escapes the network reader goroutine and terminates the client process, including during connection.start server properties or message header table parsing. This issue is fixed in version 1.13.0.
CVE-2026-77412
HIGHPre-NVD 8.98.9—Trending — 3 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.9 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
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.9Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.9
- EG Score
- 8.9(medium)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity89% × 45%Exploitation0% × 40%Automatability30% × 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 16, 2026Patch 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.0github_commit Patch Available
commit 669b42bf7b1d (rabbitmq/amqp091-go)
Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 669b42bf7b1d)
https://github.com/rabbitmq/amqp091-go/commit/669b42bf7b1db76bc6d4973e3634247f680accbfgithub_pr Patch Available
Safely handle negative x- field length.
Patch available: rabbitmq/amqp091-go v1.13.0 (PR #344 merged 2026-06-17)
https://github.com/rabbitmq/amqp091-go/pull/344github Patch Available
Denial of Service via Malicious Field Length in AMQP Client · Advisory · rabbitmq/amqp091-go · GitHub
https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-4v58-74mf-rjx3Vendor Advisories for CVE-2026-77412(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 6× in last 7d / 6× 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 00:11 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 01:56 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
Frequently asked(5)
What is CVE-2026-77412?
CVE-2026-77412 is a high vulnerability published on September 16, 2026. RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, readField in read.go reads the length of an AMQP byte-array field with type tag x into a signed int32 and passes the value directly to make when allocating the field buffer. A malicious or compromised broker can encode a value such as…
When was CVE-2026-77412 disclosed?
CVE-2026-77412 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-77412 actively exploited?
CVE-2026-77412 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-77412?
CVE-2026-77412 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-77412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77412, 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-77412
Is Your Infrastructure Affected by CVE-2026-77412?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.