https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 17 Oct 2026 07:41:31 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1125 certfr-2026-avi-1125 https://db.gcve.eu/vuln/certfr-2026-avi-1125 https://db.gcve.eu/vuln/fkie_cve-2026-67416 <p>RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.</p> <p>RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, the optimized AMQP 1.0 server_mode parser in deps/amqp10_common/src/amqp10_binary_parser.erl matches the textual prefixes of symbolic data, sequence, and value body descriptors without verifying their encoded symbol lengths. An authenticated AMQP 1.0 publisher with write permission can submit a well-formed unknown descriptor that begins with a registered body descriptor, and RabbitMQ misclassifies and stores the bytes as a standard body section. Strict AMQP 1.0 consumers can terminate while decoding the stored entry. For bodies misclassified as data, AMQP 0-9-1 or other cross-protocol conversion performs full body decoding and can terminate the consumer protocol process, with acknowledgement-required delivery permitting repeated failures. Sequence and value classifications are normally transported as opaque encoded payloads on that conversion path. The broker remains alive, and the issue does not bypass routing or authorization. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.</p> https://db.gcve.eu/vuln/fkie_cve-2026-67416 https://db.gcve.eu/vuln/rhsa-2026:82703 <p>rabbitmq-server: rabbitmq-server: Denial of Service via memory exhaustion in AMQP parser rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation rabbitmq-server: rabbitmq-server: Denial of Service via invalid MQTT PUBLISH property</p> <p>rabbitmq-server: rabbitmq-server: Denial of Service via memory exhaustion in AMQP parser rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation rabbitmq-server: rabbitmq-server: Denial of Service via invalid MQTT PUBLISH property</p> https://db.gcve.eu/vuln/rhsa-2026:82703