RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or 4294967295 instead of being rejected. An application that permits untrusted configuration of these Qos values can unintentionally request extremely large prefetch limits, allowing a broker to deliver enough queued messages to exhaust client memory and disrupt processing. This issue is fixed in version 1.13.0.
CVE-2026-77406
HIGHPre-NVD 8.28.2—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.2 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.2EG
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.2Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity82% × 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 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 3b879e1d1d25 (rabbitmq/amqp091-go)
Patch available: rabbitmq/amqp091-go v1.13.0 (contains commit 3b879e1d1d25)
https://github.com/rabbitmq/amqp091-go/commit/3b879e1d1d25b544e26b3bc3d7db3213203c0f3bgithub_pr Patch Available
Reject negative prefetch values in Qos
Patch available: rabbitmq/amqp091-go v1.13.0 (PR #351 merged 2026-06-18)
https://github.com/rabbitmq/amqp091-go/pull/351github Patch Available
Consumer Message Flooding via Signed-to-Unsigned Integer Casting in Qos Configuration · Advisory · rabbitmq/amqp091-go · GitHub
https://github.com/rabbitmq/amqp091-go/security/advisories/GHSA-rm6m-hrcw-jw33Vendor Advisories for CVE-2026-77406(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/rabbitmq/amqp091-go | — | 1.13.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
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 10:44 UTCVendor advisory
- 2026-09-18 22:04 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:45 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:46 UTCEG score recompute
- 2026-09-16 14:45 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-77406?
CVE-2026-77406 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, Channel.Qos in channel.go accepts negative prefetchCount and prefetchSize integers and casts them directly to uint16 and uint32 fields in the basic.qos method because validateQos is absent. Values such as -1 therefore wrap to 65535 or…
When was CVE-2026-77406 disclosed?
CVE-2026-77406 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-77406 actively exploited?
CVE-2026-77406 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-77406?
CVE-2026-77406 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-77406?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77406, 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
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-77406
Is Your Infrastructure Affected by CVE-2026-77406?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.