https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 16:10:34 +0000 https://vulnerability.circl.lu/vuln/fkie_cve-2026-66079 <p>RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p> <p>RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-66079 https://vulnerability.circl.lu/vuln/rhsa-2026:67552 <p>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…</p> <p>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…</p> https://vulnerability.circl.lu/vuln/rhsa-2026:67552 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-66079 <p><strong>Affected:</strong> 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</p> <p>RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p> <p><strong>Affected:</strong> 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</p> <p>RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-66079