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.
Published: 2026-09-25
Score: 2.1 Low
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized deletion of protected service accounts
Action: Patch
AI Analysis

Impact

The reported bug allows an administrator to remove users who have been marked with a protected tag by using the bulk-delete API endpoint. The protected-tag check, which normally prevents deletion of such users, is bypassed because the bulk-delete handler calls the internal deletion function directly, omitting the guard. As a result, privileged service accounts can be maliciously or accidentally removed, undermining configuration stability and potentially disrupting service continuity.

Affected Systems

Versions 3.13.0 through 3.13.15, 4.0.20, 4.1.11, and 4.2.6 of RabbitMQ Server are affected. Administrators using these releases should verify their deployment and plan for remediation.

Risk and Exploitability

The CVSS score of 2.1 indicates that the vulnerability has low overall severity. With the EPSS score unavailable and no entry in the CISA KEV catalog, the likelihood of widespread exploitation appears low at present. However, because the flaw requires administrator access to the HTTP API, an attacker who already has privileged credentials could use the bulk-delete endpoint to silently expunge protected accounts. In environments where service accounts are critical, this could lead to denial of service or configuration loss even though the vector is limited to authorized users.

Generated by OpenCVE AI on September 25, 2026 at 18:40 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade RabbitMQ Server to v3.13.15, v4.0.20, v4.1.11, v4.2.6, or a later release where the bulk-delete routine has been corrected.
  • If an upgrade cannot be performed immediately, disable the bulk-delete API for users with administrator privileges or reconfigure role‑based access control so that only authorized individuals with explicit permission can invoke bulk deletion, thereby preventing the bypass until a patch is available.
  • Audit your protected user accounts after the fix or mitigation, and confirm that no protected accounts have been deleted unexpectedly, and adjust monitoring to flag any future bulk-delete activity involving protected tags.

Generated by OpenCVE AI on September 25, 2026 at 18:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 15 Oct 2026 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Broadcom
Broadcom rabbitmq Server
CPEs cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*
Vendors & Products Broadcom
Broadcom rabbitmq Server
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H'}


Tue, 29 Sep 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sat, 26 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
First Time appeared Rabbitmq
Rabbitmq rabbitmq-server
Vendors & Products Rabbitmq
Rabbitmq rabbitmq-server

Fri, 25 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title RabbitMQ: protected tag bypass via bulk-delete
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 2.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

Broadcom Rabbitmq Server
Rabbitmq Rabbitmq-server
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-29T19:24:14.403Z

Reserved: 2026-07-23T23:25:28.898Z

Link: CVE-2026-66078

cve-icon Vulnrichment

Updated: 2026-09-29T19:24:02.933Z

cve-icon NVD

Status : Analyzed

Published: 2026-09-25T17:17:10.333

Modified: 2026-10-15T20:07:28.857

Link: CVE-2026-66078

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T11:30:09Z

Weaknesses