---
id: "CVE-2026-61547"
page: "https://infrastack.ai/live/CVE-2026-61547"
kind: "vulnerability"
aliases: ["CVE-2026-61547"]
title: "rabbitmq-c: oversized AMQP body frame causes heap overflow and memory corruption"
severity: "critical"
cvss: 9.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["amqp", "c", "cpp", "package", "rabbitmq", "rabbitmq-c"]
not_affected_if: ["no-raw-body-frames", "version-0.17.0-or-later"]
published_at: "2026-11-10T17:17:45+00:00"
first_seen_at: "2026-11-10T17:22:44+00:00"
updated_at: "2026-11-10T17:23:42+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61547", "first_seen_at": "2026-11-10T17:22:44+00:00"}]
exploit_sources: []
---

# rabbitmq-c: oversized AMQP body frame causes heap overflow and memory corruption

Link for people: https://infrastack.ai/live/CVE-2026-61547 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed rabbitmq-c version with `pkg-config --modversion rabbitmq` or your package manager's listing, and see whether it is below `0.17.0`.
- Search your code for calls to `amqp_send_frame(` that pass AMQP_FRAME_BODY frames built from data you do not control.

## Fix

- rabbitmq-c: upgrade to `0.17.0`

## Timeline

- 2026-11-10T17:22:44+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-61547

## Documents

- [advisory] Vendor advisory: github.com https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-hfjv-vcp3-39wh
- [fix] Release notes: github.com https://github.com/alanxz/rabbitmq-c/releases/tag/v0.17.0

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_