CVE-2026-68073

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.

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.

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.

An authenticated attacker could exceed the session flow control incoming window potentially leading to denial of service. This issue affects Apache Qpid Broker-J through 10.0.1.

A pre-authentication attacker could leverage unbounded symbol value caching to cause resource exhaustion leading to denial of service. Affects Apache Qpid Broker-J through 10.0.1.

A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Broker-J through 10.0.1. Users are recommended to upgrade to version 10.1.0, which fixes the issue.