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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-862"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67233.json",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "3.13.0"
},
{
"fixed": "3.13.15"
},
{
"introduced": "4.0.0"
},
{
"fixed": "4.0.20"
},
{
"introduced": "4.1.0"
},
{
"fixed": "4.1.11"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
]
}{
"extracted_events": [
{
"range": [
{
"introduced": "4.2.0"
},
{
"fixed": "4.2.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"introduced": "4.3.0"
},
{
"fixed": "4.3.1"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"original_tag": "v4.2.6",
"range": [
{
"fixed": "8a56c37f099a7bf609a555de3f0ff8ed23964d20"
}
],
"source": "REFERENCES_TAG"
},
{
"original_tag": "v4.3.1",
"range": [
{
"fixed": "49decca35e59d2cb774e5abd76412cee721308a5"
}
],
"source": "REFERENCES_TAG"
}
]
}