Direct Request ('Forced Browsing') Affecting rabbitmq-server4.2 package, versions <0:4.2.8-1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.41% (33rd 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-RHEL10-RABBITMQSERVER42-18383268
  • published29 Jul 2026
  • disclosed10 Jul 2026

Introduced: 10 Jul 2026

CVE-2026-57221  (opens in a new tab)
CWE-425  (opens in a new tab)

How to fix?

Upgrade RHEL:10 rabbitmq-server4.2 to version 0:4.2.8-1.hum1 or higher.
This issue was patched in RHSA-2026:35940.

NVD Description

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

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a virtual host to enumerate queue and exchange names and read queue message and consumer counts. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

CVSS Base Scores

version 3.1