Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67240)
Description
CVE-2026-67240 affects RabbitMQ server versions prior to 4.2.7 and 4.3.1. It involves a CPU amplification issue caused by crafted LIKE filters in AMQP 1.0 stream queues. An authenticated consumer with read and write permissions can cause significant CPU usage per message by exploiting overlapping lazy quantifiers in pattern matching. This vulnerability is fixed in versions 4.2.7 and 4.3.1.
CVSS v4.0
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions before 4.2.7 and 4.3.1 contain a vulnerability in the pattern_to_regex function used for LIKE filters in AMQP 1.0 stream queues. The function maps SQL LIKE wildcards '%' and '_' to regex patterns with overlapping lazy quantifiers, which can cause excessive backtracking and CPU usage when processing messages. An authenticated AMQP 1.0 consumer with read and write permissions on a stream queue can exploit this by attaching a receiver with a crafted filter and publishing messages with long property values, causing approximately 100-200 ms of CPU time per message. This CPU amplification can be multiplied across many messages and parallel sessions, leading to substantial resource consumption. The issue is mitigated by OTP's default match_limit and the re NIF scheduler yielding, but still represents a significant CPU amplification attack vector. The vulnerability is fixed in RabbitMQ versions 4.2.7 and 4.3.1.
Potential Impact
An attacker with authenticated AMQP 1.0 consumer access and read+write permissions on a stream queue can cause substantial CPU resource consumption on the RabbitMQ server by exploiting crafted LIKE filters that trigger excessive regex backtracking. This can degrade server performance and potentially lead to denial of service conditions under high message volume and parallel sessions.
Mitigation Recommendations
This vulnerability is fixed in RabbitMQ versions 4.2.7 and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-67240
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.04:LTS"]
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad3f5a92cdf04f6566627e7
Added to database: 10/17/2026, 22:24:41 UTC
Last enriched: 10/17/2026, 23:57:23 UTC
Last updated: 10/17/2026, 23:57:23 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.