CVE-2026-92564

In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive), the broker does not properly enforce a maximum frame size in AMQP 1.0 frames. A remote unauthenticated attacker could exploit this to cause the broker to exhaust all available memory and eventually terminate.

A session fixation vulnerability in HTTP management authentication in Apache Qpid Broker-J (through 10.1.0) allows remote attackers to gain unauthorized access to an authenticated management session by reusing a session identifier retained across successful authentication.

In Apache Qpid Broker-J versions 0.18 through 0.32, misconfiguration of ports with different authentication providers can allow a remote attacker connecting to the HTTP port to trick the broker into using an authentication provider from another port. The attacker must have valid credentials for the provider on the spoofed port.

Apache Qpid Broker-J improperly handles compressed data in the shared GZIP decompressor used for AMQP 0-8/0-9/0-9-1 and AMQP 0-10 message delivery, message conversion, and HTTP management JSON rendering. An authenticated message producer can exhaust memory and disrupt broker availability by processing data without a decompressed-output limit.

A vulnerability in Apache Qpid Broker-J (through 10.1.0) allows a pre-authentication attacker to leverage type size/count handling to cause excessive allocation. This can lead to a potential denial of service.

A vulnerability in Apache Qpid Broker-J (through 10.1.0) allows a pre-authentication attacker to leverage type size/count handling to cause excessive allocation. This can lead to a potential denial of service.

Improper handling of property-encoding exceptions during AMQP 1.0-to-AMQP 0-10 message conversion in Apache Qpid Broker-J (through 10.1.0) allows authenticated message producers to disrupt delivery to AMQP 0-10 consumers. This occurs via message properties that the target encoder does not handle correctly.

In Apache Qpid Broker-J through 10.0.1, it was not possible to govern the rate at which the broker would respond to an echo flow, enabling an authenticated attacker to cause excessive resource usage and potential denial of service. The issue is fixed in version 10.1.0.

In Apache Qpid Broker-J through 10.0.1, it was not possible to govern the maximum number of transfer frames per incoming delivery, enabling an authenticated attacker to cause excessive resource usage and potential denial of service.

An authenticated attacker can craft a disposition frame with large or illegal ranges causing excessive CPU usage due to naive range handling, leading to denial of service. This issue affects Apache Qpid Broker-J through 10.0.1.