PatchSiren cyber security CVE debrief
CVE-2026-92573 Apache Software Foundation CVE debrief
CVE-2026-92573 Improper handling of compressed data in Apache Qpid Broker-J allows authenticated message producers to exhaust memory and disrupt broker availability. Defenders should assess exposure and upgrade to version 10.1.1. The issue affects Apache Qpid Broker-J through 10.1.0. Users are recommended to upgrade to version 10.1.1, which fixes the issue. The vulnerability is related to 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.
- Vendor
- Apache Software Foundation
- Product
- Apache Qpid Broker-J
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-25
- Original CVE updated
- 2026-09-25
- Advisory published
- 2026-09-25
- Advisory updated
- 2026-09-25
Who should care
Defenders of Apache Qpid Broker-J deployments should assess exposure and upgrade to version 10.1.1. They should also verify decompressed-output limits for GZIP decompressor and monitor broker availability and memory usage. Additionally, they should review compensating controls for exposed systems while remediation is scheduled and verified.
Why it matters
CVE-2026-92573 allows authenticated message producers to exhaust memory and disrupt broker availability in Apache Qpid Broker-J. Defenders should upgrade to version 10.1.1 and verify decompressed-output limits.
- Memory exhaustion and broker availability disruption
- Need to upgrade to version 10.1.1 to fix the issue
- Verify decompressed-output limits for GZIP decompressor
Technical summary
Improper handling of 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 allows authenticated message producers to exhaust memory and disrupt broker availability via processing without a decompressed-output limit. The issue affects Apache Qpid Broker-J through 10.1.0. Users are recommended to upgrade to version 10.1.1, which fixes the issue. The vulnerability is related to 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.
Defensive priority
Upgrade to version 10.1.1 to fix the issue.
Recommended defensive actions
- Upgrade Apache Qpid Broker-J to version 10.1.1
- Review and limit decompressed-output for GZIP decompressor
- Monitor broker availability and memory usage
- Verify decompressed-output limits for GZIP decompressor
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability in Apache Qpid Broker-J. The issue allows authenticated message producers to exhaust memory and disrupt broker availability via processing without a decompressed-output limit. The CVE record was published on 2026-09-25T09:17:06.837Z and has not been modified since then. The NVD entry provides additional information on the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-92573 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-92573
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-92573 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92573
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://lists.apache.org/thread/461lhqt1r4g1mq3oyrcscphxzlhxlv1y
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.