CVE-2026-66078: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, protected tag bypass via bulk-delete. dELETE /api/users/:name refuses to delete users tagged protected (rabbitmgmtwmuser:deleteresource/2 checks isprotecteduser). POST /api/users/bulk-delete iterates the supplied username list and calls rabbitauthbackendinternal:deleteuser/2 directly , that function has no protected-tag check , so the guard is silently An administrator can delete protected-tagged service accounts via the bulk endpoint, bypassing a safeguard the test suite confirms is rabbitmqmanagement enabled Attacker has the administrator tag A protected-tagged user. This issue is fixed in versions 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6.
AI Analysis
Technical Summary
RabbitMQ versions 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, and 4.2.0 to 4.2.5 contain a missing authorization check (CWE-862) in the bulk-delete users API endpoint. While the single user delete API enforces a check to prevent deletion of users tagged as protected, the bulk-delete endpoint bypasses this check by directly invoking an internal delete user function without verifying the protected tag. As a result, an attacker with administrator privileges can delete protected-tagged service accounts, circumventing intended safeguards. The vulnerability is resolved in the specified fixed versions.
Potential Impact
An attacker with administrator privileges can delete protected-tagged service accounts via the bulk-delete API endpoint, bypassing the protection that normally prevents deletion of these accounts. This could disrupt service accounts critical to RabbitMQ operations. The vulnerability requires administrator privileges and does not allow privilege escalation or remote code execution. The CVSS 4.0 score is 2.1, indicating low severity.
Mitigation Recommendations
Upgrade to rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later, where this issue is fixed. No other mitigation is indicated. Since this is a server-side software vulnerability, patching is the recommended and effective remediation.
CVE-2026-66078: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
Description
RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6, protected tag bypass via bulk-delete. dELETE /api/users/:name refuses to delete users tagged protected (rabbitmgmtwmuser:deleteresource/2 checks isprotecteduser). POST /api/users/bulk-delete iterates the supplied username list and calls rabbitauthbackendinternal:deleteuser/2 directly , that function has no protected-tag check , so the guard is silently An administrator can delete protected-tagged service accounts via the bulk endpoint, bypassing a safeguard the test suite confirms is rabbitmqmanagement enabled Attacker has the administrator tag A protected-tagged user. This issue is fixed in versions 3.13.15 and 4.0.20 and 4.1.11 and 4.2.6.
CVSS v4.0
Score 2.1low
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, and 4.2.0 to 4.2.5 contain a missing authorization check (CWE-862) in the bulk-delete users API endpoint. While the single user delete API enforces a check to prevent deletion of users tagged as protected, the bulk-delete endpoint bypasses this check by directly invoking an internal delete user function without verifying the protected tag. As a result, an attacker with administrator privileges can delete protected-tagged service accounts, circumventing intended safeguards. The vulnerability is resolved in the specified fixed versions.
Potential Impact
An attacker with administrator privileges can delete protected-tagged service accounts via the bulk-delete API endpoint, bypassing the protection that normally prevents deletion of these accounts. This could disrupt service accounts critical to RabbitMQ operations. The vulnerability requires administrator privileges and does not allow privilege escalation or remote code execution. The CVSS 4.0 score is 2.1, indicating low severity.
Mitigation Recommendations
Upgrade to rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later, where this issue is fixed. No other mitigation is indicated. Since this is a server-side software vulnerability, patching is the recommended and effective remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-23T23:25:28.898Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a25af7a7c54106018e25
Added to database: 09/25/2026, 16:33:30 UTC
Last enriched: 09/25/2026, 16:49:01 UTC
Last updated: 09/26/2026, 02:44:21 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.