CVE-2026-67233: rabbitmq-server · Missing Authorization
Affects rabbitmq-serverSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium · fixed in 4.3.1 : update rabbitmq-server when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.1, 4.2.6, 4.1.11 +2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 24 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
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade rabbitmq-server to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.1 or later where this issue is fixed. The vendor advisory confirms these versions contain the official fix. No additional mitigation is required once upgraded.
Description
CVE-2026-67233 is a missing authorization vulnerability in rabbitmq-server affecting the shovel management resource. Prior to fixed versions, users with the monitoring tag, intended for read-only access, could delete or restart shovels in any vhost they could see. This is due to insufficient role checks on DELETE operations in the shovel management API. The issue requires the rabbitmq_shovel and rabbitmq_shovel_management plugins to be enabled. It is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.