Bug 2540102 - CVE-2026-67405 rabbitmq-server: RabbitMQ: Cross-Site WebSocket Hijacking via missing Origin header validation [fedora-all]
Summary: CVE-2026-67405 rabbitmq-server: RabbitMQ: Cross-Site WebSocket Hijacking via ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["0a78f1c9-5bbe-45ea-a9ff-0...
Depends On:
Blocks: CVE-2026-67405
TreeView+ depends on / blocked
 
Reported: 2026-09-24 14:09 UTC by Jon Weiser
Modified: 2026-10-09 15:45 UTC (History)
2 users (show)

Fixed In Version: rabbitmq-server-4.3.6-1.fc46 rabbitmq-server-4.3.6-1.fc45 rabbitmq-server-4.2.9-2.fc44
Clone Of:
Environment:
Last Closed: 2026-10-09 15:44:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Weiser 2026-09-24 14:09:04 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. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, Neither the Web-MQTT handler (deps/rabbitmq_web_mqtt/src/rabbit_web_mqtt_handler.erl:104) nor the Web-STOMP handler (deps/rabbitmq_web_stomp/src/rabbit_web_stomp_handler.erl:102) validates the Origin header on the WebSocket upgrade. Under ssl_cert_login=true, the browser presents the client certificate automatically, so an attacker's JavaScript running in the victim's browser can authenticate as the victim. Preconditions include The non-default configuration use_http_auth=true (Web-STOMP) or ssl_cert_login=true (both plugins) must be enabled. The issue is harmless under the default in-band CONNECT credential configuration.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

Comment 1 Peter Lemenkov 2026-10-09 13:24:38 UTC
This issue is already fixed upstream in RabbitMQ 4.3.6, which is the version currently built for Fedora rawhide (rabbitmq-server-4.3.6-1.fc46) and Fedora 45 (rabbitmq-server-4.3.6-1.fc45).

Fedora 44 (currently 4.2.9) and Fedora 43 (currently 4.0.9) still need attention; backports/rebases for the still-supported stable branches are being worked on. Leaving this report open to track that remaining work.

Comment 2 Peter Lemenkov 2026-10-09 15:44:27 UTC
This issue is already addressed in the rabbitmq-server builds currently shipped in all maintained Fedora branches:

  * Fedora rawhide: rabbitmq-server-4.3.6-1.fc46
  * Fedora 45:      rabbitmq-server-4.3.6-1.fc45
  * Fedora 44:      rabbitmq-server-4.2.9-2.fc44

No new build is required for these branches, so closing as CURRENTRELEASE.

Fedora 43 (rabbitmq-server-4.0.9) will NOT be updated for this CVE batch: the upstream 4.0.x line ended at 4.0.9 (later 4.0.x fixes are commercial-only, with no public OSS release) and Fedora 43 reaches end of life on 2026-12-09, so a backport to F43 is not worthwhile.


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