<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 15:15:24 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-67405</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-67405</link>
      <description>&lt;p&gt;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&amp;#39;s JavaScript running in the victim&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s JavaScript running in the victim&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-67405</guid>
    </item>
    <item>
      <title>RHSA-2026:67552 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2026:67552</link>
      <description>&lt;p&gt;rabbitmq-server: RabbitMQ: Unsanitized vhost names allow for XSS in management UI rabbitmq: RabbitMQ: Authenticated user can bypass connection limits via stream protocol rabbitmq: RabbitMQ: Information disclosure of decrypted Shovel URIs in debug logs rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters rabbitmq-server: RabbitMQ: Cross-Origin Resource Sharing (CORS) misconfiguration allows unauthorized actions rabbitmq-server: RabbitMQ: Denial of Service via atom table exhaustion in stream chunk_selector rabbitmq: RabbitMQ: Denial of Service via management API regular expression filter rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw rabbitmq: RabbitMQ: Information disclosure via cross-vhost authorization bypass RabbitMQ: RabbitMQ: Account takeover via stored Cross-Site Scripting in TLS peer-certificate DN rabbitmq-server: RabbitMQ: Denial of Service via AMQP 1.0 array32 parsing rabbitmq-server: RabbitMQ: Denial of Service via unbounded super-stream partition allocation rabbitmq-server: RabbitMQ: Privilege escalation via super-stream HTTP creation rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion rabbitmq: RabbitMQ: Information disclosure of AMQP 1.0 shovel URI passwords rabbitmq: RabbitMQ: Administrator path traversal allows arbitrary file write rabbitmq: RabbitMQ: Denial of Service vi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rabbitmq-server: RabbitMQ: Unsanitized vhost names allow for XSS in management UI rabbitmq: RabbitMQ: Authenticated user can bypass connection limits via stream protocol rabbitmq: RabbitMQ: Information disclosure of decrypted Shovel URIs in debug logs rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters rabbitmq-server: RabbitMQ: Cross-Origin Resource Sharing (CORS) misconfiguration allows unauthorized actions rabbitmq-server: RabbitMQ: Denial of Service via atom table exhaustion in stream chunk_selector rabbitmq: RabbitMQ: Denial of Service via management API regular expression filter rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw rabbitmq: RabbitMQ: Information disclosure via cross-vhost authorization bypass RabbitMQ: RabbitMQ: Account takeover via stored Cross-Site Scripting in TLS peer-certificate DN rabbitmq-server: RabbitMQ: Denial of Service via AMQP 1.0 array32 parsing rabbitmq-server: RabbitMQ: Denial of Service via unbounded super-stream partition allocation rabbitmq-server: RabbitMQ: Privilege escalation via super-stream HTTP creation rabbitmq: RabbitMQ: Denial of Service via unbounded consistent-hash exchange weight rabbitmq-server: RabbitMQ: Denial of Service via JMS topic exchange atom exhaustion rabbitmq: RabbitMQ: Information disclosure of AMQP 1.0 shovel URI passwords rabbitmq: RabbitMQ: Administrator path traversal allows arbitrary file write rabbitmq: RabbitMQ: Denial of Service vi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2026:67552</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-67405</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-67405</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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&amp;#39;s JavaScript running in the victim&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;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&amp;#39;s JavaScript running in the victim&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-67405</guid>
    </item>
  </channel>
</rss>
