Quick answers
- Is CVE-2026-66074 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66074 being exploited in the wild.
- How severe is CVE-2026-66074?
- Informational severity, published 23 September 2026.
- Which products and versions are affected?
- RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.
- Is there a fix for CVE-2026-66074?
- A patch was published on 2026-04-23: Versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 contain the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66074 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-66074?
- Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The match_value/3 function passes user-supplied regex patterns to Erlang's re:run without enforcing a match_limit, executing the regex once per resource in the result set. With a large dataset (e.g., 5000 queues), a single request can consume excessive CPU time, and parallel requests saturate scheduler threads. Precondition is possession of the management tag; the use_regex=true parameter is a supported feature on list endpoints, making this reachable through normal API use.
Affected products
- RabbitMQ RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5
Timeline
- 2026-09-23: disclosed
- 2026-04-23: patched: Versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 contain the fix