Incorrect Authorization Affecting erlang-rabbitmq-client package, versions <4.1.5-160000.2.1


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
0.35% (27th 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-SLES1600-ERLANGRABBITMQCLIENT-20187058
  • published28 Sept 2026
  • disclosed22 Sept 2026

Introduced: 22 Sep 2026

NewCVE-2026-57217  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade SLES:16.0.0 erlang-rabbitmq-client to version 4.1.5-160000.2.1 or higher.

NVD Description

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

RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.21, 4.1.11, and 4.2.6, RabbitMQ topic authorization can allow restricted topic writes and binds during metadata-store failures because topic-permission lookup errors from Khepri can collapse to undefined, which the internal backend treats as allow. This issue is fixed in versions 3.13.15, 4.0.21, 4.1.11, and 4.2.6.

CVSS Base Scores

version 3.1