Bug 2539779 (CVE-2026-67405) - CVE-2026-67405 rabbitmq-server: RabbitMQ: Cross-Site WebSocket Hijacking via missing Origin header validation
Summary: CVE-2026-67405 rabbitmq-server: RabbitMQ: Cross-Site WebSocket Hijacking via ...
Keywords:
Status: NEW
Alias: CVE-2026-67405
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2540102
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-23 20:52 UTC by OSIDB Bzimport
Modified: 2026-09-24 14:09 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-23 20:52:27 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.