https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-04T03:13:27.527767+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-rabbitmq-2026-67411 BIT-rabbitmq-2026-67411 — RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass 2026-10-04T03:13:27.531178+00:00

Affected: Bitnami: rabbitmq

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.

 https://cve.radiocsirt.org/vuln/euvd-2026-376218 EUVD-2026-376218 2026-10-04T03:13:27.531245+00:00 EUVD-2026-376218 https://cve.radiocsirt.org/vuln/fkie_cve-2026-67411 fkie_cve-2026-67411 2026-10-04T03:13:27.531262+00:00

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.

 https://cve.radiocsirt.org/vuln/msrc_cve-2026-67411 msrc_CVE-2026-67411 — RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass 2026-10-04T03:13:27.531287+00:00 msrc_CVE-2026-67411 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-67411 UBUNTU-CVE-2026-67411 2026-10-04T03:13:27.531302+00:00

Affected: Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:18.04:LTS: rabbitmq-server, Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server, Ubuntu:26.04:LTS: rabbitmq-server

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.