BIT-rabbitmq-2026-66078

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-66078.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-rabbitmq-2026-66078
Aliases
Published
2026-10-01T09:32:56Z
Modified
2026-10-16T09:45:25Z
Summary
RabbitMQ: protected tag bypass via bulk-delete
Details

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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
    ],
    "severity": "Medium"
}
References

Affected packages

Bitnami / rabbitmq

Package

Name
rabbitmq
Purl
pkg:bitnami/rabbitmq

Severity

  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
3.13.0
Fixed
3.13.15
Introduced
4.0.0
Fixed
4.0.20
Introduced
4.1.0
Fixed
4.1.11
Introduced
4.2.0
Fixed
4.2.6

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-66078.json"