CVE-2026-61547: rabbitmq-c corruption in amqp_send

Summary

rabbitmq-c, a C client library for RabbitMQ's AMQP protocol, has a heap buffer overflow in amqp_send_frame() that lets an attacker remotely, without logging in, trigger an out-of-bounds write to heap memory, which can crash the process and corrupt memory.

Read the original 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.

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
Reach?/20Unknown. No tracked technology or package matched
Severity9.8/10CVSS 9.8
No patch0/5No signal

What would change the score

Would score about 72 if added to CISA KEV
Would score about 67 if CISA's SSVC rates exploitation active
Would score about 32 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

Upgrade to a fixed version: 0.17.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-61547 (rabbitmq-c: Heap Buffer Overflow in amqp_send_frame() When Serializing Oversized AMQP_FRAME_BODY), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-61547 (entry last updated 2026-11-10):
Affected:
- alanxz rabbitmq-c: fixed in 0.17.0
Fixed versions: 0.17.0.
Conditions (all must be true for the bug to be hit):
- Affected versions are rabbitmq-c 0.16.0 and earlier. (source: https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-hfjv-vcp3-39wh)
- The application passes an oversized body frame to amqp_send_frame(). (source: https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-hfjv-vcp3-39wh)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-61547 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61547 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-hfjv-vcp3-39wh
- https://github.com/alanxz/rabbitmq-c/pull/892
- https://github.com/alanxz/rabbitmq-c/releases/tag/v0.17.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-61547
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-61547.

Timeline

Nov 10, 2026, 4:21 PM UTCCVE published
Nov 10, 2026, 4:25 PM UTCFirst seen by cve.now
Nov 10, 2026, 4:38 PM UTCPosted on X by cve.now

Affected versions

alanxz rabbitmq-c
fixed in 0.17.0

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · alanxz/rabbitmq-c · Advisory GHSA-hfjv-vcp3-39wh

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-61547
Record
NVD · CVE-2026-61547

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-61547

Is CVE-2026-61547 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

When amqp_send_frame() serializes an AMQP_FRAME_BODY that is larger than it should be, it can write past the end of a heap buffer. The advisory describes this as a heap out-of-bounds write.Source: github.com

Which versions are affected by CVE-2026-61547?

rabbitmq-c: before 0.17.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions rabbitmq-c 0.16.0 and earlier are affected, but only in applications that pass an oversized body frame to the public amqp_send_frame() API. To check, look at the installed rabbitmq-c version and whether application code calls amqp_send_frame().Source: github.com

How do I fix CVE-2026-61547?

Upgrade rabbitmq-c to 0.17.0 or later, which contains the fix.Source: github.com

rabbitmq-c: Heap Buffer Overflow in amqp_send_frame() When Serializing Oversized AMQP_FRAME_BODY