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

CVE record · `CVE-2026-61547`

- **Identifiers:** `CVE-2026-61547`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **CNA:** GitHub_M
- **Weakness (CWE):** [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [alanxz rabbitmq-c](https://agentprime.io/advisories/technology/alanxz-rabbitmq-c.md)
- **Published:** 10 Nov 2026
- **Updated:** 14 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: GitHub_M) at 10 Nov 2026, 16:21 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected products, as the CNA wrote them

- Vendor: alanxz. Product: rabbitmq-c.
  - affected: `< 0.17.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> rabbitmq-c versions before 0.17.0 have a heap buffer overflow in amqp_send_frame() when an application passes an oversized AMQP_FRAME_BODY frame. The source does not state what network or account access an attacker would need, but exploitation can cause a heap out-of-bounds write, leading to process crash and memory corruption. Upgrade to rabbitmq-c 0.17.0 or later.

Written 19 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 9.8 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0057, the 48th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 10 Nov 2026, 16:21 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-61547)
- 10 Nov 2026, 16:27 UTC: First seen by agentprime
- 10 Nov 2026, 17:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-61547)

## Sources

- [CVE List: CVE-2026-61547](https://www.cve.org/CVERecord?id=CVE-2026-61547)
- [NVD: CVE-2026-61547](https://nvd.nist.gov/vuln/detail/CVE-2026-61547)

### References from the CNA

- <https://github.com/alanxz/rabbitmq-c/security/advisories/GHSA-hfjv-vcp3-39wh> (confirm)
- <https://github.com/alanxz/rabbitmq-c/pull/892>
- <https://github.com/alanxz/rabbitmq-c/releases/tag/v0.17.0>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-61547>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-61547/>. Everything for agents: <https://agentprime.io/llms.txt>.
