Skip to main content
VulnerabilityPublished Updated

CVE-2026-67228: Atom exhaustion · to_atom on runtime-parameter component

Affects rabbitmqSource GCVE Database

0
Compare
Authoritative record:CVE-2026-67228· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.3.1 or 4.2.7 when convenient.

Data as of 17 Nov 2026, 16:19 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.3.1, 4.2.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade rabbitmq to 4.3.1 or 4.2.7.

Affected software

ProductAffectedFixed in
Bitnamirabbitmqpkg:bitnami/rabbitmqOther threatsAffected
  • >=4.2.0 <4.2.7
  • >=4.3.0 <4.3.1
Fixed in
  • 4.2.7
  • 4.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade RabbitMQ to versions 4.2.7 or 4.3.1 or later, where this vulnerability is fixed. No other mitigation is indicated or required by the vendor advisory.

Description

RabbitMQ versions prior to 4.2.7 and 4.3.1 contain a vulnerability where the runtime-parameters lookup path converts the :component segment of a request URL into a new Erlang atom without checking if it already exists. Because the Erlang atom table is bounded and atoms are not garbage collected, an attacker with policymaker privileges can exhaust the atom table by issuing roughly one million requests with distinct component values, causing the RabbitMQ node to crash and resulting in a denial of service. This issue is fixed in versions 4.2.7 and 4.3.1.

References

Community reviews

Loading reviews…