Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The amqp091-go Go library, versions before 1.13.0, does not enforce the negotiated frame_max limit on content body frames. A malicious or compromised AMQP broker can send an oversized body frame after connection setup, causing the client to allocate large amounts of memory, which can lead to out-of-memory crashes. Upgrade to version 1.13.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.9 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0055, the 46th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-6c5v-hqjr-5xxp
- OSV: GHSA-6c5v-hqjr-5xxp
- github.com/rabbitmq/amqp091-go/security/advisories/GHSA-6c5v-hqjr-5xxp
- nvd.nist.gov/vuln/detail/CVE-2026-79921
- github.com/rabbitmq/amqp091-go/pull/353
- github.com/rabbitmq/amqp091-go/commit/6beb7b51f59e46ddcf8066ad498dad32491d3be0
- github.com/rabbitmq/amqp091-go
- github.com/rabbitmq/amqp091-go/releases/tag/v1.13.0