CVE-2026-66078

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-25 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-15 20:07 UTC Last updatedMost recent change to the record

Details

Published

2026-09-25 17:17 UTC

Last modified

2026-10-15 20:07 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-862 · Missing authorization

Record status

Analyzed

Affected

• Broadcom Rabbitmq Server < 3.13.15
• Broadcom Rabbitmq Server < 4.0.20
• Broadcom Rabbitmq Server < 4.1.11
• Broadcom Rabbitmq Server < 4.2.6

Attack profile CVSS 4.0 · 2.1

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

High

User interaction

None

Confidentiality

None

Integrity

Low

Availability

None