Resource Exhaustion Affecting rabbitmq-server package, versions <4.0.5-10ubuntu5.2


Severity

Recommended
medium

Based on Ubuntu security rating.

Threat Intelligence

EPSS
0.33% (24th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-UBUNTU2604-RABBITMQSERVER-20126232
  • published16 Oct 2026
  • disclosed23 Sept 2026

Introduced: 23 Sep 2026

NewCVE-2026-67238  (opens in a new tab)
CWE-400  (opens in a new tab)

How to fix?

Upgrade Ubuntu:26.04 rabbitmq-server to version 4.0.5-10ubuntu5.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rabbitmq-server package and not the rabbitmq-server package as distributed by Ubuntu. See How to fix? for Ubuntu:26.04 relevant fixed versions and status.

RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, rabbit_pid_codec:decompose_from_binary/1 parses a caller-supplied ETF-encoded binary and calls binary_to_atom(Node, utf8) on the node-name field. It is reached from rabbit_volatile_queue:pid_from_name/2, which is invoked for any queue name / routing key beginning amq.rabbitmq.reply-to.. The CandidateNodes membership check happens after the atom is created, and the surrounding try/catch cannot reclaim atoms (they are never GC'd). binary_to_existing_atom is not used. Any authenticated AMQP client can crash the entire Erlang VM (all vhosts, all connections) with ~1M cheap requests. Preconditions include Authenticated AMQP 0-9-1 connection to any vhost No per-connection rate limit low enough to make ~1M operations infeasible. This issue is fixed in versions 4.2.7 and 4.3.1.

CVSS Base Scores

version 3.1