# CVE-2026-92608: Apache Qpid Broker-J improper AMQP message property encoding exception handling

Source: https://junglewise.ai/threats/cve-2026-92608-improper-handling-of-property-encoding-exceptions-in-amqp-1-0-to  
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-92608 · Severity: high · CVSS 7.5 · Published 2026-09-25

Apache Qpid Broker-J is an enterprise message broker that handles AMQP protocol messaging. Authenticated message producers can craft malformed message properties that crash or disrupt message delivery to AMQP 0-10 consumers, causing message loss and service disruption.

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-92608 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92608 being exploited in the wild.

**How severe is CVE-2026-92608?** High severity, with a CVSS score of 7.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-92608?** 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-92608 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-92608?** 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 vulnerability exists in the AMQP 1.0-to-AMQP 0-10 message conversion logic, where improper exception handling of property-encoding failures allows authenticated producers to inject messages with properties that the target encoder cannot process. An authenticated network attacker can exploit this to cause denial of service by disrupting message delivery without requiring user interaction or special privileges beyond message production rights.

## 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/rklst4cz1g0nkpzkpho7kjmy4gnx1ppc](https://lists.apache.org/thread/rklst4cz1g0nkpzkpho7kjmy4gnx1ppc)

## Related threats

- [Apache Qpid Broker-J GZIP decompression denial of service](https://junglewise.ai/threats/cve-2026-92573-improper-handling-of-compressed-data-in-the-shared-gzip)
- [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)