Vulnerability Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the Web STOMP WebSocket handler enforced neither max_frame_size nor login_timeout before authentication, allowing an unauthenticated client to keep a connection alive with a slow stream of small frames and accumulate unbounded pre-authentication state. The rabbitmq_web_stomp plugin must be enabled, and no authentication is required to reach the vulnerable path. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-server/commit/0b4080fa5d6f797b6331d0ce1db2b
- https://github.com/rabbitmq/rabbitmq-server/commit/8138edae6d2beaafe699a41a754d1
- https://github.com/rabbitmq/rabbitmq-server/commit/c1000ba89052608c01c052d980164
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-7v63-j4gm-p
FAQ
What is CVE-2026-67230?
CVE-2026-67230 is a documented vulnerability. RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the Web STOMP WebSocket handler enforced neither max_frame_size nor login_timeout before authenticat...
How severe is CVE-2026-67230?
CVSS scoring is not yet available for CVE-2026-67230. Check NVD for updates.
Is there a patch for CVE-2026-67230?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.