Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
GHSA-w6r9-248c-frg8: amqp091-go versions before 1.14.0 can be made to allocate memory based on a frame size declared by the peer before connection negotiation completes, bypassing the frame-size limit added in 1.13.0. An attacker who controls a malicious or compromised AMQP broker, or a peer able to supply the transport during connection setup, can send a small frame header declaring a very large body, which may exhaust client memory and terminate the process. Upgrade to github.com/rabbitmq/amqp091-go 1.14.0 or later. No workaround is listed.
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 |
|---|---|---|---|---|
| 6.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0049, the 42nd percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:11 UTC First seen by agentprime
- 31 Oct 2026, 14:11 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w6r9-248c-frg8
- OSV: GHSA-w6r9-248c-frg8
- github.com/rabbitmq/amqp091-go/security/advisories/GHSA-w6r9-248c-frg8
- github.com/rabbitmq/amqp091-go/pull/377
- github.com/rabbitmq/amqp091-go/commit/6723e8cff8710f0a6bf5fb4af375e285052535b3
- github.com/rabbitmq/amqp091-go
- github.com/rabbitmq/amqp091-go/releases/tag/v1.14.0