Inefficient Regular Expression Complexity Affecting rabbitmq-server4.3 package, versions <0:4.3.6-1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.38% (32nd 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-RABBITMQSERVER43-20073576
  • published24 Sept 2026
  • disclosed23 Sept 2026

Introduced: 23 Sep 2026

NewCVE-2026-66074  (opens in a new tab)
CWE-1333  (opens in a new tab)

How to fix?

Upgrade RHEL:10 rabbitmq-server4.3 to version 0:4.3.6-1.hum1 or higher.
This issue was patched in RHSA-2026:67552.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rabbitmq-server4.3 package and not the rabbitmq-server4.3 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 versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, match_value/3 passes the user-supplied ?name= regular expression to re:run with no match_limit option, and executes it once per resource in the result set. OTP's default 10M match_limit caps each call at roughly 100-200ms, but the regex runs once per resource in the result set. With a large set, for example 5000 queues at 150ms each, a single request consumes 12 or more minutes of CPU. Parallel requests saturate the schedulers. The use_regex=true option is a supported feature on list endpoints, so this path is reachable through normal API use. Preconditions include Any user with the management tag can exploit this.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

CVSS Base Scores

version 3.1