Quick answers
- Is CVE-2026-77409 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77409 being exploited in the wild.
- How severe is CVE-2026-77409?
- Informational severity, published 16 September 2026.
- Which products and versions are affected?
- RabbitMQ Amqp091-Go prior to 1.13.0.
- Is there a fix for CVE-2026-77409?
- A patch was published on 2026-06-16: Version 1.13.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77409 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-77409?
- Check whether you run RabbitMQ Amqp091-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a deadlock condition in the Go AMQP 0.9.1 client library. Channel.dispatch in channel.go, confirms.confirm in confirms.go, and Connection.dispatch0 in connection.go synchronously send publisher confirmations, flow-control events, consumer cancellations, returned messages, and connection block notifications to application-provided channels without timeouts. If a listener channel is unbuffered, full, or not drained promptly, the sole reader goroutine blocks and stops processing frames, acknowledgments, deliveries, and heartbeats. Under burst event scenarios, this causes connection stalls, missed heartbeats, deadlocks, and disconnections. The fix in version 1.13.0 adds a 5-second timeout to notification sends to prevent reader goroutine blocking.
Affected products
- RabbitMQ amqp091-go prior to 1.13.0
Timeline
- 2026-09-16: disclosed
- 2026-06-16: patched: Version 1.13.0 released with fix