All vulnerabilities

Servers and applications

CVE-2026-67228

Atom exhaustion: to_atom on runtime-parameter component

Severity
Medium 6.9
Published
9 Jul 2026
Last changed
30 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
4.2.7, 4.3.1
Exploit chance
0.3% in the next 30 daysHigher than 25% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Uncontrolled resource consumption (CWE-400)
Attack
Over the network · Needs an administrator account · No user action needed
Attacker can
Take it down
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-73qp-fwh4-2q5g
Sources
NVD, Project advisories (GitHub)

Description

This vulnerability was identified by Team RabbitMQ and/or other teams at Broadcom, not via a responsible disclosure from an external researcher.

lookup_component/1 calls rabbit_data_coercion:to_atom(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.

The runtime-parameters lookup path coerces the URL :component segment to an atom with rabbit_data_coercion:to_atom/1 in lookup_component/1 (deps/rabbit/src/rabbit_runtime_parameters.erl), creating a new atom for any previously unseen value. A safe helper, rabbit_registry:binary_to_type/1, which uses binary_to_existing_atom with a catch, already exists but is not used at this call site.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 4.2.0 before 4.2.7
  • From 4.3.0 before 4.3.1
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 up to 3.13.22
  • From 4.0.0 up to 4.0.25
  • From 4.1.0 up to 4.1.18
  • From 4.2.0 before 4.2.7
  • From 4.3.0 before 4.3.1

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67228
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67228
  • GitHub Advisory Database https://github.com/advisories/GHSA-73qp-fwh4-2q5g
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-73qp-fwh4-2q5g