Skip to main content
VulnerabilityPublished Updated

CVE-2026-67240: RabbitMQ · ReDoS via AMQP 1.0 SQL filter LIKE wildcard

Affects rabbitmqSource GCVE Database

0
Compare
Authoritative record:CVE-2026-67240· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 4.3.1 or 4.2.7 when convenient.

Data as of 17 Nov 2026, 16:19 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.3.1, 4.2.7
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade rabbitmq to 4.3.1 or 4.2.7.

Affected software

ProductAffectedFixed in
Bitnamirabbitmqpkg:bitnami/rabbitmqOther threatsAffected
  • >=4.2.0 <4.2.7
  • >=4.3.0 <4.3.1
Fixed in
  • 4.2.7
  • 4.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade RabbitMQ to versions 4.2.7 or 4.3.1 or later, where this vulnerability is fixed. The vendor has provided official patches in these releases. No additional mitigation is required if these versions are deployed.

Description

RabbitMQ versions prior to 4.2.7 and 4.3.1 contain a Regular Expression Denial of Service (ReDoS) vulnerability in the AMQP 1.0 SQL filter LIKE wildcard implementation. An authenticated AMQP 1.0 consumer with read and write permissions on stream queues can cause significant CPU consumption by crafting a LIKE filter pattern that triggers excessive regex backtracking. This can amplify CPU usage per message, potentially impacting performance under load. The issue is fixed in RabbitMQ versions 4.2.7 and 4.3.1.

References

Community reviews

Loading reviews…