CVE-2026-67230: RabbitMQ is a messaging and streaming broker.

High CVSS 7.5

CVE id
CVE-2026-67230
Published
Last modified

Affected packages

PackageAffected versionsFixed in
RabbitMQ
Runtimes and servers
>= 3.13.0, < 3.13.15
>= 4.0.0, < 4.0.20
>= 4.1.0, < 4.1.11
>= 4.2.0, < 4.2.6
3.13.15, 4.0.20, 4.1.11, 4.2.6

How to fix it

Upgrade RabbitMQ to the fixed release of the line you run: 3.13.15, 4.0.20, 4.1.11, 4.2.6.

rabbitmqctl version
  • Upgrade RabbitMQ (the rabbitmq image tag or the rabbitmq-server package) to the patched release, node by node.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

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 maxframesize nor logintimeout 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 rabbitmqweb_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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.