Skip to content
Fencer Vulns
medium 6.5

CVE-2026-67240 json

RabbitMQ: ReDoS via AMQP 1.0 SQL filter LIKE wildcard

published 2026-09-23 46 d ago modified 2026-10-30 9 d ago also BIT-rabbitmq-2026-67240 , EUVD-2026-85636 , GHSA-59c5-553c-57m2

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, pattern_to_regex maps % -> .*? and _ -> ., then compiles ^...$ with only [unicode]; re:run is called with only [{capture, none}] - no explicit match_limit. A pattern like %_%_..._%X becomes ^.*?..*?.....*?.X$ with overlapping lazy quantifiers. The whole-expression cap is ?MAX_EXPRESSION_LENGTH=4096 chars / ?MAX_TOKENS=200; a LIKE string literal is one token, so ~2000 %_ pairs fit. SQL filters are accepted unconditionally at rabbit_amqp_session.erl:3264 (no feature flag). Evaluated per-message at rabbit_stream_queue.erl:1439. OTP's default 10M match_limit caps each match at ~100-200 ms (not seconds), and the re NIF yields to the scheduler. An authenticated AMQP 1.0 consumer with read+write on a stream queue can cause ~100-200 ms of CPU per delivered message via a crafted LIKE filter, multiplied across thousands of messages and parallel sessions - a substantial backtracking-driven CPU amplification. Preconditions include AMQP 1.0 with stream queues in use Attacker can attach a receiver with a filter (read permission) and publish messages with long property values (write permission). This issue is fixed in versions 4.2.7 and 4.3.1.

Patch / fix

  • bitnami rabbitmq 4.2.7, 4.3.1
  • vmware rabbitmq 4.2.7, 4.3.1
  • pivotal_software rabbitmq 4.2.7, 4.3.1
  • rabbitmq-server Debian 14 4.3.2-1

debian advisories DEBIAN-CVE-2026-67240

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-67240 updated cvss 6.5

RabbitMQ: RabbitMQ: Denial of Service via crafted AMQP 1.0 SQL LIKE filter

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: no fix planned “Will not fix”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix RHSA-2026:67552

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
45 d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-59c5-553c-57m2 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
CNA 4.0 2.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=4.2.0, <4.2.7
>=4.3.0, <4.3.1
4.2.7
4.3.1

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness
  • CWE-1333 Inefficient Regular Expression Complexity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.