Skip to content
Heist/ feed
Back to feed
MediumFix available

RabbitMQ: protected tag bypass via bulk-delete

Type: advisorySources: OSV

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.

Products
rabbitmq
Affected versions
Not specified
Fixed versions
3.13.15, 4.0.20, 4.1.11, 4.2.6
CVEs
CVE-2026-66078
Confirmed fixed CVEs
Not specified
Updated in this feed
30 Oct 2026, 19:52 UTC · Revision 1

Source evidence

RabbitMQ: protected tag bypass via bulk-delete

core-osv · Original source

Published 1 Oct 2026, 09:32 UTC

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.

osv:BIT-rabbitmq-2026-66078

rabbitmq

Fixed versions: 3.13.15, 4.0.20, 4.1.11, 4.2.6

Complete source record
{
  "id": "41d844dcc9618f4ab4e77278c9d829b68e370f85dba686a320a956e853d9e025",
  "url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-66078",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "RabbitMQ: protected tag bypass via bulk-delete",
    "summary": "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.",
    "evidence": "osv:BIT-rabbitmq-2026-66078",
    "products": [
      {
        "name": {
          "value": "rabbitmq",
          "evidence": "/affected/0/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "3.13.15",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.0.20",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.1.11",
            "evidence": "/affected/0/ranges"
          },
          {
            "value": "4.2.6",
            "evidence": "/affected/0/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "BIT-rabbitmq-2026-66078",
      "aliases": [
        "BIT-rabbitmq-2026-66078",
        "CVE-2026-66078",
        "GHSA-j9m2-hw6x-rqr9"
      ],
      "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"
                }
              ]
            }
          ],
          "package": {
            "name": "rabbitmq",
            "purl": "pkg:bitnami/rabbitmq",
            "ecosystem": "Bitnami"
          },
          "severity": [
            {
              "type": "CVSS_V3",
              "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H"
            }
          ],
          "database_specific": {
            "source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-66078.json"
          }
        }
      ],
      "modified": "2026-10-16T09:45:20.664770731Z",
      "provider": "osv",
      "references": [
        "https://github.com/rabbitmq/rabbitmq-server/commit/e5b890a64b42ec1f79a8e9d735512150cf77479c",
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6",
        "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-j9m2-hw6x-rqr9",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-66078"
      ],
      "provider_metadata": {
        "cpes": [
          "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
        ],
        "severity": "Medium"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-66078",
        "evidence": "/aliases"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/database_specific/severity"
  },
  "source_id": "core-osv",
  "document_id": 338392,
  "published_at": "2026-10-01T09:32:56.977+00:00"
}