CVE-2026-61547: alanxz rabbitmq-c · Out-of-bounds Write
Affects alanxz rabbitmq-cSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 0.17.0 as a priority.
Data as of 10 Nov 2026, 16:34 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.0 | 9.8 |
|---|
- Patch
- Available – fixed in 0.17.0
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade alanxz rabbitmq-c to 0.17.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| alanxzrabbitmq-c | Affected
| Fixed in
|
Description
rabbitmq-c is a C-language AMQP client library for RabbitMQ. Prior to version 0.17.0, a heap buffer overflow exists in rabbitmq-c when the public amqp_send_frame() API is used to serialize an oversized AMQP_FRAME_BODY. The issue occurs because amqp_frame_to_bytes() copies frame.payload.body_fragment.len bytes into the connection outbound buffer without validating that the body fragment fits within the allocated frame buffer. An application that passes an oversized body frame to amqp_send_frame() can trigger a heap out-of-bounds write, resulting in process crash and memory corruption. This issue has been patched in version 0.17.0.