Quick answers
- Is CVE-2026-67230 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67230 being exploited in the wild.
- How severe is CVE-2026-67230?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- RabbitMQ 3.13.0–3.13.14, 4.0.0–4.0.19, 4.1.0–4.1.10, 4.2.0–4.2.5.
- Is there a fix for CVE-2026-67230?
- A patch was published on 2026-09-25: Fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67230 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67230?
- 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 Web STOMP WebSocket handler in RabbitMQ fails to enforce max_frame_size or login_timeout constraints before client authentication, allowing unauthenticated clients to send arbitrarily small frames indefinitely and accumulate unbounded pre-authentication connection state. An attacker can exploit this with network access to keep connections alive and drain server resources without authentication. The vulnerability requires the rabbitmq_web_stomp plugin to be enabled and affects versions 3.13.0–3.12.14, 4.0.0–4.0.19, 4.1.0–4.1.10, and 4.2.0–4.2.5.
Affected products
- RabbitMQ RabbitMQ 3.13.0–3.13.14, 4.0.0–4.0.19, 4.1.0–4.1.10, 4.2.0–4.2.5
Timeline
- 2026-09-25: disclosed: Vulnerability published on NVD
- 2026-09-25: patched: Fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6