Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
Telegraf may stop processing messages due to blocked channel
published 1 month ago
Summary
Versions of Telegraf before 1.31.0‑34 use a RabbitMQ library that can get stuck when an internal communication channel fills up. When this happens the program stops handling incoming data, heartbeats and can lose its connection to the broker. Upgrade Telegraf to 1.31.0‑34 or later (which includes the library fix) to prevent the stall.
What to do
- Update telegraf to version 1.31.0-34.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| Azure Linux:3 | – | telegraf |
< 1.31.0-34 <= 1.31.0-33 Fix: upgrade to 1.31.0-34
|
| Azure Linux:3 | azure | telegraf | <= 1.31.0-31 |
Original advisory text
CVE-2026-77409 affecting package telegraf for versions less than 1.31.0-34
RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, 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, including NotifyConfirm events and connection block notifications, to application-provided channels. If a listener channel is unbuffered, full, or not drained promptly, the sole reader goroutine blocks and stops processing frames, acknowledgments, deliveries, and heartbeats. Broker-driven event bursts can therefore cause connection stalls, missed heartbeats, deadlocks, and disconnection. This issue is fixed in version 1.13.0.
References
Timeline
Published16 Sep 2026
Updated2 Nov 2026
First seen19 Sep 2026
Sources
AZL-103281 · OSV
Track software like this
Free during beta