CVE-2026-67411: RabbitMQ is a messaging and streaming broker.
High CVSS 7.1
- CVE id
- CVE-2026-67411
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 3.13.0, < 3.13.18 >= 4.0.0, < 4.0.23 >= 4.1.0, < 4.1.14 >= 4.2.0, < 4.2.9 >= 4.3.0, < 4.3.3 |
3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 3.13.18, 4.0.23, 4.1.14, 4.2.9, 4.3.3.
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.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.
References
- CVE-2026-67411 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-67411
- Web: https://github.com/rabbitmq/rabbitmq-server/commit/a7528314840c4f8dc9904684f9f97ffa7aac6349
- Web: https://github.com/rabbitmq/rabbitmq-server/commit/edbead0eabbd65925d0dc914a22d6a29e155e646
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6
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.
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.