All vulnerabilities
CVE-2026-66078GHSA-j9m2-hw6x-rqr9

rabbitmq-server: RabbitMQ: protected tag bypass via bulk-delete

rabbitmq rabbitmq-server
Open in ThreatlineRecord JSON
CVSS
2.1Low
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 29 Sep 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.38%Chance of exploitation activity in the next 30 days, higher than 30% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
Published25 Sep 2026Updated 29 Sep 2026CVE List

What fixes it

No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.

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.

Text from CVE List

Affected versions 4

  • rabbitmq-serveraffected: >= 3.13.0, < 3.13.15CVE List
  • rabbitmq-serveraffected: >= 4.0.0, < 4.0.20CVE List
  • rabbitmq-serveraffected: >= 4.1.0, < 4.1.11CVE List
  • rabbitmq-serveraffected: >= 4.2.0, < 4.2.6CVE List

References 3