---
id: CVE-2026-67230
title: RabbitMQ is a messaging and streaming broker
summary: >-
  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 clie…
severity: medium
cvss: 6.3
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N'
cwe:
  - CWE-770
vendor: rabbitmq
product: rabbitmq-server
affected:
  - 'rabbitmq-server >= 4.2.0, < 4.2.6'
  - 'rabbitmq-server >= 4.1.0, < 4.1.11'
  - 'rabbitmq-server >= 4.0.0, < 4.0.20'
  - 'rabbitmq-server >= 3.13.0, < 3.13.15'
published: '2026-09-25'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T17:17:11.600'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-67230'
references:
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/0b4080fa5d6f797b6331d0ce1db2b4bacd34560e
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/8138edae6d2beaafe699a41a754d17420bdc2068
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/commit/c1000ba89052608c01c052d98016403ba6e92222
    label: security-advisories@github.com
  - url: 'https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6'
    label: security-advisories@github.com
  - url: >-
      https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-7v63-j4gm-p4rh
    label: security-advisories@github.com
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-09-25T17:13:14.030Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.