CVE-2026-67411: rabbitmq-server · Incorrect Authorization
Affects rabbitmq-serverSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 4.3.3 : update rabbitmq-server when convenient.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.3, 4.2.9, 4.1.14 +2
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
GitHubrabbitmq/rabbitmq-serverpkg:github/rabbitmq/rabbitmq-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability has been fixed in rabbitmq-server versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3. Users should upgrade to these or later versions to remediate the issue. No other mitigations are indicated or required by the vendor advisory.
Description
CVE-2026-67411 is an incorrect authorization vulnerability in rabbitmq-server affecting native MQTT and MQTT over WebSocket when used behind a trusted PROXY Protocol frontend. Versions from 3.13.0 up to but not including 3.13.18, 4.0.0 up to 4.0.23, 4.1.0 up to 4.1.14, 4.2.0 up to 4.2.9, and 4.3.0 up to 4.3.3 are affected. The flaw allows an attacker with valid credentials for a loopback-restricted account to bypass source-address restrictions due to loss of the proxy-derived client address before authentication checks. Password authentication is still required. The issue has been fixed in the specified later versions.
References
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-4r6f-9cpw-f6g6 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/a7528314840c4f8dc9904684f9f97ffa7aac6349 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/edbead0eabbd65925d0dc914a22d6a29e155e646 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3 (opens in a new tab)