Bug 2566805 - CVE-2026-67411 rabbitmq-server: rabbitmq-server: Access control bypass via PROXY protocol handling in MQTT [fedora-all]
Summary: CVE-2026-67411 rabbitmq-server: rabbitmq-server: Access control bypass via PR...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["a035f2f3-2f82-4250-85e8-6...
Depends On:
Blocks: CVE-2026-67411
TreeView+ depends on / blocked
 
Reported: 2026-11-04 10:23 UTC by Mauro Matteo Cascella
Modified: 2026-11-19 01:46 UTC (History)
2 users (show)

Fixed In Version: rabbitmq-server-4.0.9-7.fc43
Clone Of:
Environment:
Last Closed: 2026-11-19 01:46:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mauro Matteo Cascella 2026-11-04 10:23:15 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3, native MQTT and MQTT over WebSocket behind a trusted PROXY Protocol frontend could lose the proxy-derived client address before the MQTT authentication path checked loopback_users, causing the frontend-to-broker address to be treated as loopback. An attacker who can reach the trusted frontend and has valid credentials for a loopback-restricted account can therefore bypass the source-address restriction; the issue does not bypass password authentication. This issue is fixed in versions 3.13.18, 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

Comment 1 Peter Lemenkov 2026-11-04 15:43:43 UTC
This issue is fixed upstream in RabbitMQ 4.2.9 and 4.3.3. Fedora 45 and rawhide ship rabbitmq-server-4.3.7, and Fedora 44 ships rabbitmq-server-4.2.9, so both are already fixed.

The Fedora 43 (4.0.9) status is still being evaluated.

Comment 2 Fedora Update System 2026-11-04 18:15:05 UTC
FEDORA-2026-ea1afc0a7b (rabbitmq-server-4.0.9-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

Comment 3 Fedora Update System 2026-11-05 16:08:56 UTC
FEDORA-2026-ea1afc0a7b has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ea1afc0a7b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 4 Fedora Update System 2026-11-19 01:46:18 UTC
FEDORA-2026-ea1afc0a7b (rabbitmq-server-4.0.9-7.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.