cve.bz

CVE-2026-67233 broadcom rabbitmq server: Missing Authorization

6.0 mediumEPSS 0.3%

Medium (6.0) in broadcom rabbitmq server. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, The shovel management resource's is_authorized/2 delegates to rabbit_mgmt_util:is_authorized_monitor/2, which accepts the monitoring tag. But allowed_methods includes DELETE, and delete_resource/2 deletes / restarts shovel runtime parameters with no additional role check. A monitoring user , intended to have read-only visibility , can therefore delete or restart any shovel in any vhost they can see. A read-only monitoring user can delete or restart any dynamic shovel , a state-changing operation that the equivalent /api/parameters endpoint correctly restricts to policymaker. Preconditions include rabbitmq_shovel + rabbitmq_shovel_management plugins enabled Attacker has credentials with the monitoring tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-862 Missing Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67233 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67233?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67233?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67233 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 3.13.0 before 3.13.15
broadcom:rabbitmq_serverfrom 4.0.0 before 4.0.20
broadcom:rabbitmq_serverfrom 4.1.0 before 4.1.11
broadcom:rabbitmq_serverfrom 4.2.0 before 4.2.6
broadcom:rabbitmq_serverfrom 4.3.0 before 4.3.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13rabbitmq-serverno fix listedDEBIAN-CVE-2026-67233
Debian14rabbitmq-server4.3.2-1DEBIAN-CVE-2026-67233
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 morerabbitmq-serverno fix listedUBUNTU-CVE-2026-67233
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-server3.13.7-10AZL-105780

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat rates this flaw Moderate. To exploit it, an attacker needs broker credentials with the monitoring tag and network access to the management HTTP listener, and the broker must have the rabbitmq_shovel and rabbitmq_shovel_management plugins enabled. The monitoring role check has no per-vhost scope, so one monitoring account can delete or restart shovels in every virtual host on the broker, including vhosts where it holds no permissions. The attacker gains no read access and cannot create or modify shovels. The broker and unrelated clients keep running; the impact is limited to message flow through the targeted shovels until an administrator recreates them. An attacker who keeps the credentials can repeat the deletion, so rotating or removing the account should come before restoring the shovels.

Red Hat's mitigation

Disable the shovel management extension on brokers that do not need to manage shovels over HTTP. Enable rabbitmq_shovel explicitly first so it stays active if it was only pulled in as a dependency:

rabbitmq-plugins enable rabbitmq_shovel

rabbitmq-plugins disable rabbitmq_shovel_management

This removes the /api/shovels endpoint. Accounts with the policymaker or administrator tag can still delete shovels through /api/parameters, which enforces the correct role check. If the endpoint has to stay available, remove the monitoring tag from any account that should not be able to stop message flow.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverNot affected
Red Hat OpenStack Platform 16.2rabbitmq-serverNot affected
Red Hat OpenStack Platform 17.1rabbitmq-serverNot affected
Red Hat OpenStack Platform 18.0rabbitmq-serverNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67233.

Attack patterns (CAPEC)

  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON