https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 14:28:59 +0000 https://vulnerability.circl.lu/vuln/bit-rabbitmq-2026-67419 <p><strong>Affected:</strong> Bitnami: rabbitmq</p> <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> <p><strong>Affected:</strong> Bitnami: rabbitmq</p> <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> https://vulnerability.circl.lu/vuln/bit-rabbitmq-2026-67419 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1125 certfr-2026-avi-1125 https://vulnerability.circl.lu/vuln/certfr-2026-avi-1125 https://vulnerability.circl.lu/vuln/fkie_cve-2026-67419 <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-67419 https://vulnerability.circl.lu/vuln/msrc_cve-2026-67419 msrc_CVE-2026-67419 https://vulnerability.circl.lu/vuln/msrc_cve-2026-67419 https://vulnerability.circl.lu/vuln/rhsa-2026:67552 <p>rabbitmq-server: RabbitMQ: Unsanitized vhost names allow for XSS in management UI rabbitmq-server: RabbitMQ: Information disclosure via improper access control in AMQP management endpoint 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-server: Denial of service via atom exhaustion in OAuth2 JWT scope parsing rabbitmq-server: RabbitMQ: Denial of Service via atom table exhaustion in stream chunk_selector rabbitmq-server: rabbitmq-server: Denial of Service via management API atom table exhaustion 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: Protected account deletion safeguard bypass via bulk-delete API 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 vi…</p> <p>rabbitmq-server: RabbitMQ: Unsanitized vhost names allow for XSS in management UI rabbitmq-server: RabbitMQ: Information disclosure via improper access control in AMQP management endpoint 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-server: Denial of service via atom exhaustion in OAuth2 JWT scope parsing rabbitmq-server: RabbitMQ: Denial of Service via atom table exhaustion in stream chunk_selector rabbitmq-server: rabbitmq-server: Denial of Service via management API atom table exhaustion 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: Protected account deletion safeguard bypass via bulk-delete API 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 vi…</p> https://vulnerability.circl.lu/vuln/rhsa-2026:67552 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-67419 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:Pro:18.04:LTS: rabbitmq-server, Ubuntu:Pro:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server, Ubuntu:26.10: rabbitmq-server, Ubuntu:26.04:LTS: rabbitmq-server</p> <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:Pro:18.04:LTS: rabbitmq-server, Ubuntu:Pro:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server, Ubuntu:26.10: rabbitmq-server, Ubuntu:26.04:LTS: rabbitmq-server</p> <p>RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-67419