CVE-2026-67228: RabbitMQ is a messaging and streaming broker.
Medium CVSS 4.9
- CVE id
- CVE-2026-67228
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 4.2.0, < 4.2.7 >= 4.3.0, < 4.3.1 |
4.2.7, 4.3.1 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 4.2.7, 4.3.1.
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.2.7 and 4.3.1, The runtime-parameters lookup path coerces the URL :component segment to an atom with rabbitdatacoercion:toatom/1 in lookupcomponent/1 (deps/rabbit/src/rabbitruntimeparameters.erl), creating a new atom for any previously unseen value. A safe helper, rabbitregistry:binarytotype/1, which uses binarytoexistingatom with a catch, already exists but is not used at this call site. lookupcomponent/1 calls rabbitdatacoercion:toatom(Component) on the :component segment of the request URL, converting an attacker-supplied string into a new atom. Because the Erlang atom table is bounded and atoms are never garbage collected, an authorized policymaker issuing roughly one million requests with distinct component values can exhaust the atom table and crash the node, resulting in a denial of service. Preconditions include Exploitation requires policymaker privileges and roughly one million requests.. This issue is fixed in versions 4.2.7 and 4.3.1.
References
- CVE-2026-67228 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-67228
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-73qp-fwh4-2q5g
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.