# CVE-2026-67414: RabbitMQ AMQP 1.0 parser: amplification memory-exhaustion DoS via zero-width array aggregation


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** BIT-rabbitmq-2026-67414, DEBIAN-CVE-2026-67414, GHSA-w6mq-4qpx-v7mh, UBUNTU-CVE-2026-67414

## What is CVE-2026-67414?

CVE-2026-67414 is a medium-severity vulnerability in rabbitmq-server, published on 14 Oct 2026. 

### Official description

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-67414?

1 open source package ship an affected version, including rabbitmq.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rabbitmq` | Bitnami | From 4.0.0 | 4.0.24, 4.1.15, 4.2.10, 4.3.4 |

## How do I fix CVE-2026-67414?

Upgrade rabbitmq to a fixed version for your release line: 4.0.24, 4.1.15, 4.2.10 or 4.3.4.

## Is CVE-2026-67414 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67414 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67414 and fix it if it is affected.

What it is: CVE-2026-67414 is a medium-severity vulnerability in rabbitmq-server, published on 14 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67414 exists.

Affected packages and fixed versions:
- rabbitmq (Bitnami): affected from 4.0.0; fixed in 4.0.24, 4.1.15, 4.2.10, 4.3.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67414/ (Markdown: https://insights.sbomify.com/CVE-2026-67414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67414
- OSV: https://osv.dev/vulnerability/CVE-2026-67414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67414/
Summaries are generated and may contain mistakes; the official description above is the record.