Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

Buy Us a Coffee

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

Quick assessment

Affected

rabbitmq rabbitmq-server

Exploitation

No confirmed in-the-wild exploitation; assess based on exposure

Recommended action

Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

RabbitMQ 是一个消息和流处理代理。在 3.13.0 到 3.13.17（不包括 3.13.18）、4.0.0 到 4.0.22（不包括 4.0.23）、4.1.0 到 4.1.13（不包括 4.1.14）、4.2.0 到 4.2.8（不包括 4.2.9），以及 4.3.0 到 4.3.2（不包括 4.3.3）版本中，当 RabbitMQ 使用受信任的前端代理（支持 PROXY Protocol）来承载原生 MQTT 或基于 WebSocket 的 MQTT 连接时，可能在 MQTT 认证流程检查之前丢失了

CVSS 6.0 · Medium EPSS 0.39% · P31 Updated Sep 28, 2026

Get alerts for future matching vulnerabilities Log in to subscribe

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!

View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title

RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass

Source: CVE Program / CVE List V5

Vulnerability 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.

Source: CVE Program / CVE List V5

CVSS Information

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

Source: CVE Program / CVE List V5

Vulnerability Type

授权机制不正确

Source: CVE Program / CVE List V5

Affected Products

Vendor	Product	Affected Versions	CPE	Subscribe
rabbitmq	rabbitmq-server	>= 4.3.0, < 4.3.3	-

II. Public POCs for CVE-2026-67411

#	POC Description	Source Link	Shenlong Link

AI-Generated POC Premium

No public POC found.

III. Intelligence Information for CVE-2026-67411

请登录查看更多情报信息。

Other References for CVE-2026-67411 (5)

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

https://www.cve.org/CVERecord?id=CVE-2026-67411

Same Patch Batch · rabbitmq · 2026-09-25 · 28 CVEs total

CVE-2026-67236	8.2 HIGH	RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /
CVE-2026-67409	8.2 HIGH	RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Au
CVE-2026-67410	8.2 HIGH	RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
CVE-2026-67239	7.6 HIGH	RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
CVE-2026-67237	7.5 HIGH	RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint
CVE-2026-67408	7.1 HIGH	RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node
CVE-2026-67419	7.1 HIGH	RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
CVE-2026-67226	6.9 MEDIUM	RabbitMQ: Admin-only atom exhaustion: PUT /api/users tags list
CVE-2026-61837	6.3 MEDIUM	RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authent
CVE-2026-67242	6.3 MEDIUM	RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp
CVE-2026-67230	6.3 MEDIUM	RabbitMQ: Web-STOMP unbounded pre-auth accumulation
CVE-2026-67223	6.3 MEDIUM	RabbitMQ: LDAP DN injection via unescaped substitution
CVE-2026-67225	6.3 MEDIUM	RabbitMQ: Stream-protocol frame length never validated against frame_max
CVE-2026-66073	6.0 MEDIUM	RabbitMQ: Atom table exhaustion via management API node field
CVE-2026-67412	6.0 MEDIUM	RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message acces
CVE-2026-67413	6.0 MEDIUM	RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an U
CVE-2026-66071	6.0 MEDIUM	RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values
CVE-2026-67415	5.9 MEDIUM	RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Servic
CVE-2026-67222	5.9 MEDIUM	RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client
CVE-2026-67227	5.9 MEDIUM	RabbitMQ: Atom exhaustion: to_atom on global-parameter :name

Showing top 20 of 28 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

Same product: rabbitmq-server

Same vendor: rabbitmq

Same weakness: CWE-863

V. Comments for CVE-2026-67411

No comments yet

Goal Reached Thanks to every supporter — we hit 100%!

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

Quick assessment

I. Basic Information for CVE-2026-67411

Vulnerability Information

Vulnerability Title

Vulnerability Description

CVSS Information

Vulnerability Type

Affected Products

II. Public POCs for CVE-2026-67411

III. Intelligence Information for CVE-2026-67411

Other References for CVE-2026-67411 (5)

Same Patch Batch · rabbitmq · 2026-09-25 · 28 CVEs total

IV. Related Vulnerabilities

V. Comments for CVE-2026-67411

Leave a comment