CVE-2026-67235: RabbitMQ is a messaging and streaming broker.
Medium CVSS 6.5
- CVE id
- CVE-2026-67235
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 3.13.0, < 3.13.15 >= 4.0.0, < 4.0.20 >= 4.1.0, < 4.1.11 >= 4.2.0, < 4.2.6 |
3.13.15, 4.0.20, 4.1.11, 4.2.6 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 3.13.15, 4.0.20, 4.1.11, 4.2.6.
rabbitmqctl version
- Upgrade RabbitMQ (the rabbitmq image tag or the rabbitmq-server package) to the patched release, node by node.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
RabbitMQ is a messaging and streaming broker. Prior to versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15, The content-header BodySize (a uint64) was stored without validation against maxmessagesize. The size check ran only when assembly completed. By declaring bodysize = 2^63-1 and then streaming fragments, a client ensured that checkmsg_size never fired, so the accumulated body size went unbounded. A reader process accumulates memory until the memory alarm fires, degrading all publishers cluster-wide, or until the node runs out of memory. The memory alarm provides only partial mitigation, since it is reactive rather than preventive. AMQP 0-9-1 is the most widely used protocol, and any publisher can trigger this condition. Preconditions include Any authenticated AMQP 0-9-1 client with publish permission can exploit this.. This issue is fixed in versions 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15.
References
- CVE-2026-67235 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-67235
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q8g2-pc7m-m3jw
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.