Client disconnection via synchronous notification channel blocking
Published Sep 16, 2026 · Updated Sep 18, 2026
Denial of service in RabbitMQ amqp091-go before 1.13.0 allows remote attackers to stall AMQP clients through broker-driven events. Channel.dispatch, confirms.confirm, and Connection.dispatch0 synchronously send events to application channels, so a full or undrained listener blocks the sole frame-reading goroutine. Exploitation requires influence over broker activity or a malicious broker plus an application listener that cannot drain the burst; the resulting stall drops heartbeats and disconnects the client.
Summary
What happened
Denial of service in RabbitMQ amqp091-go before 1.13.0 allows remote attackers to stall AMQP clients through broker-driven events. Channel.dispatch, confirms.confirm, and Connection.dispatch0 synchronously send events to application channels, so a full or undrained listener blocks the sole frame-reading goroutine. Exploitation requires influence over broker activity or a malicious broker plus an application listener that cannot drain the burst; the resulting stall drops heartbeats and disconnects the client.
The record
- CVE
- CVE-2026-77409
- Published
- Sep 16, 2026
- Updated
- Sep 18, 2026
- Vendor
- RabbitMQ
- Product
- amqp091-go
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.13.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started