CVE-2026-61547 · Package
NO FIX YET · SEE WHAT TO DO
rabbitmq-c, a C client library for RabbitMQ, fails to check body frame size when serializing with amqp_send_frame(), causing a heap out-of-bounds write. An attacker can crash the process and corrupt memory, and the sources do not state code execution.
first public Jul 2, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Applications written in C or C++ that link rabbitmq-c and call the public amqp_send_frame() API with body frames. The sources describe the trigger as an application passing an oversized body fragment, so applications that only use higher-level publish helpers or never send raw body frames may be less exposed. Services that build body frames from untrusted input are the main concern. The sources do not say whether the bug is reachable from the network without application code doing this.
Not affected if no-raw-body-frames, version-0.17.0-or-later
Who cares amqp, c, cpp, rabbitmq, rabbitmq-c
pkg-config --modversion rabbitmq or your package manager's listing, and see whether it is below 0.17.0.amqp_send_frame( that pass AMQP_FRAME_BODY frames built from data you do not control.0.17.0rabbitmq-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.
This page as .md · .json · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.