# CVE-2026-92573: Apache Qpid Broker-J GZIP decompression denial of service

Source: https://junglewise.ai/threats/cve-2026-92573-improper-handling-of-compressed-data-in-the-shared-gzip  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-92573 · Severity: medium · CVSS 6.5 · Published 2026-09-25

Apache Qpid Broker-J is an AMQP message broker used to route and deliver enterprise messages. An authenticated attacker can send specially crafted compressed messages that cause the broker to exhaust memory and become unavailable, disrupting message delivery and business operations.

Technologies: [Apache Qpid Broker-J](https://junglewise.ai/threats/technologies/qpid-broker-j). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-92573 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92573 being exploited in the wild.

**How severe is CVE-2026-92573?** Medium severity, with a CVSS score of 6.5, published 25 September 2026.

**Which products and versions are affected?** Apache Qpid Broker-J through 10.1.0.

**Is there a fix for CVE-2026-92573?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-92573 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-92573?** Check whether you run Apache Qpid Broker-J at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The shared GZIP decompressor in Qpid Broker-J lacks a decompressed-output limit when processing AMQP 0-8/0-9/0-9-1 and AMQP 0-10 messages during message delivery, conversion, and HTTP management JSON rendering. An authenticated message producer can exploit this by sending compressed payloads that decompress to extremely large sizes, exhausting broker memory and causing denial of service. The vulnerability requires authentication to exploit.

## Affected products

- Apache Qpid Broker-J through 10.1.0

## Timeline

- 2026-09-25: disclosed

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://lists.apache.org/thread/461lhqt1r4g1mq3oyrcscphxzlhxlv1y](https://lists.apache.org/thread/461lhqt1r4g1mq3oyrcscphxzlhxlv1y)

## Related threats

- [Apache Qpid Broker-J stack overflow in type parsing](https://junglewise.ai/threats/cve-2026-92564-a-pre-authentication-attacker-could-leverage-type-nesting-to)
- [Apache Qpid Broker-J memory exhaustion denial of service](https://junglewise.ai/threats/cve-2026-92560-a-pre-authentication-attacker-could-leverage-type-size-count)
- [Apache Qpid Broker-J denial of service via type allocation](https://junglewise.ai/threats/cve-2026-92550-a-pre-authentication-attacker-could-leverage-type-size-count)
- [Apache Qpid Broker-J session fixation in HTTP management authentication](https://junglewise.ai/threats/cve-2026-92609-session-fixation-in-http-management-authentication-allows-remote)
- [Apache Qpid Broker-J improper AMQP message property encoding exception handling](https://junglewise.ai/threats/cve-2026-92608-improper-handling-of-property-encoding-exceptions-in-amqp-1-0-to)