BIT-rabbitmq-2026-67405
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67405.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rabbitmq-2026-67405
- Aliases
-
- CVE-2026-67405
- GHSA-9c4f-rxxm-88q3
- Published
- 2026-10-01T09:33:43Z
- Modified
- 2026-10-01T10:10:53Z
- Summary
- RabbitMQ: CSWSH on Web-STOMP / Web-MQTT (no Origin validation)
- Details
-
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.
- Database specific
{ "cpes": [ "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*" ], "severity": "Medium" }- References
Affected packages
Bitnami / rabbitmq
Package
- Name
- rabbitmq
- Purl
- pkg:bitnami/rabbitmq
Severity
- 5.3 (Medium) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator