GHSA-jwgh-mqvv-gpfh
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed AMQP broker port
-
ExploitSend crafted 0-8/0-9/0-9-1 frame
-
ExecutionOversized type size/count triggers huge allocation
-
ImpactBroker heap exhausted, service crashes
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory allocation limits
|
| Exploitation Conditions | Exploitation requires network access to a Qpid Broker-J instance (through 10.1.0) that exposes an AMQP 0-8/0-9/0-9-1 protocol listener; the malformed type size/count frame is processed by the decoder BEFORE authentication, so no credentials, user interaction, or non-default configuration are needed as long as a legacy AMQP 0-8/0-9/0-9-1 listener is enabled and reachable. The primary limiting factors are: the broker must be network-reachable by the attacker (mitigated if the AMQP port is firewalled to trusted clients), and the affected protocol path is specifically the AMQP 0-8/0-9/0-9-1 decoder - deployments using only AMQP 1.0 may not be on this code path. Impact is limited to availability (crash/resource exhaustion); no data disclosure or code execution results. |
| Impact | This is a pre-authentication denial-of-service in the AMQP 0-8/0-9/0-9-1 protocol decoder of Apache Qpid Broker-J, where attacker-controlled type size/count fields drive excessive memory allocation (classic CWE-770 uncontrolled resource allocation). No CVSS vector, CWE, EPSS, KEV, or POC data is provided by any source, so quantitative exploitation signals are entirely absent - the only severity anchor is Apache's own qualitative rating of 'important'. Reconstructing the vector, the flaw is remotely reachable before authentication with low complexity and no user interaction, but impact is confined to availability (A:H, no confidentiality/integrity), yielding an assessed ~7.5. Real-world risk is moderate and product-scoped: exploitation is trivial in principle (send malformed AMQP frames to an exposed broker port) but the payoff is only a crash/resource-exhaustion DoS, not code execution or data theft, and Qpid Broker-J has a limited deployment footprint. No public exploit is identified at time of analysis and there is no evidence of active exploitation, so this is a patch-in-normal-cycle issue rather than an emergency - with the caveat that brokers exposing AMQP listeners to untrusted networks should prioritize the upgrade because the pre-auth reachability removes any authentication barrier. |
| Exploit ScenarioDerived | An attacker with network reach to an exposed Qpid Broker-J AMQP listener sends a crafted AMQP 0-8/0-9/0-9-1 frame containing oversized type size or element-count values before authenticating. The decoder trusts these values and pre-allocates a large buffer or collection, exhausting heap memory and driving the broker to OutOfMemory/crash, denying messaging service to legitimate clients. No public exploit code is identified at time of analysis, but the attack requires no credentials and only low complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 25, 2026
Pre-authentication denial of service in Apache Qpid Broker-J (through 10.1.0) allows a remote attacker to exhaust broker memory or crash it by sending a malformed AMQP 0-8/0-9/0-9-1 frame whose type size/count fields drive an oversized allocation; the decoder handles this frame before authentication is performed, so the assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (availability-only impact, no data disclosure or code execution). Exploitation only requires network reachability to an enabled legacy AMQP 0-8/0-9/0-9-1 listener, so deployments that exclusively use AMQP 1.0 are not on the affected code path, and firewalling the AMQP port to trusted clients removes exposure. There is no public exploit code identified at time of analysis and no confirmed active exploitation (CISA KEV).
RemediationAI
Vendor-released patch: upgrade Apache Qpid Broker-J to 10.1.1, which fixes the issue, per the oss-security advisory (https://seclists.org/oss-sec/2026/q3/927) and the project site (https://qpid.apache.org/). If an immediate upgrade is not possible, disable or remove the legacy AMQP 0-8/0-9/0-9-1 listener/port so the decoder is never reachable; the trade-off is loss of connectivity for clients that still speak those protocol versions, and any port exposed for legacy compatibility should instead be firewalled to trusted client networks. Because the flaw is triggered pre-authentication, relying on broker authentication or ACLs provides no protection on an exposed legacy listener, and resource caps or JVM heap limits only reduce, rather than eliminate, the availability impact.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Qpid Broker-J is a pure-Java AMQP message broker; the vulnerable component is the legacy AMQP 0-8/0-9/0-9-1 protocol plugin (Maven artifact org.apache.qpid:qpid-broker-plugins-amqp-0-8-protocol), which parses wire-level frames such as field tables, arrays, and long strings that carry attacker-controlled size and count prefixes. Because the decoder trusts those declared lengths and allocates buffers proportional to them without validating them against the actual frame length or configured memory limits, an unauthenticated peer that can reach the listener can force excessive allocation, matching the CWE-770 uncontrolled resource allocation class identified in the independent assessment. The allocation happens during frame decoding, ahead of the authentication exchange, which is why the assessed vector carries PR:N and N/UI and why no credentials are required. The attack surface is limited to deployments that enable and expose the legacy 0-8/0-9/0-9-1 protocol path; AMQP 1.0-only configurations do not exercise this decoder.
Know when Qpid Broker J gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Pre-authentication network-reachable decoder flaw (AV:N/PR:N/UI:N, low complexity) causing memory-exhaustion DoS with availability-only impact, no confidentiality or integrity effect.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
2Description PRE-NVD
Articles & Coverage 1
Executive ViewAI
Apache Qpid Broker-J deployments running versions through 10.1.0 with enabled legacy AMQP 0-8/0-9/0-9-1 listeners face an unauthenticated remote denial-of-service risk that can exhaust broker memory or crash the service before authentication is performed. This is an availability-focused issue with no data disclosure or code execution, and there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV). Leadership should care because a broker outage could disrupt messaging-dependent business services, but exposure is limited to legacy listeners and can be reduced by disabling or firewalling those endpoints while patching is unavailable.
No vendor-released patch identified at time of analysis. Disable or firewall AMQP 0-8/0-9/0-9-1 listeners, restrict AMQP ports to trusted clients, migrate to AMQP 1.0-only, and monitor broker memory/CPU and logs for malformed frames or crashes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Qpid Broker J
View allIn Apache Qpid Broker-J 0.18 through 0.32, if the broker is configured with different authentication providers on differ
Session fixation in the HTTP management interface of Apache Qpid Broker-J through 10.1.0 lets remote, unauthenticated at
The AMQP 0-8, 0-9, 0-91, and 0-10 connection handling in Apache Qpid Java before 6.0.3 might allow remote attackers to b
In Apache Qpid Broker-J versions 6.1.0 through 6.1.4 (inclusive) the broker does not properly enforce a maximum frame si
The Apache Qpid Broker for Java can be configured to use different so called AuthenticationProviders to handle user auth
Unauthenticated remote denial of service in Apache Qpid Broker-J through 10.1.0, where a crafted AMQP 0-8/0-9/0-9-1 fiel
Pre-authentication denial of service in Apache Qpid Broker-J through 10.1.0: a remote attacker who can reach a broker wi
Denial of service in Apache Qpid Broker-J through 10.1.0 allows an authenticated AMQP 1.0 message producer to disrupt me
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which all
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 7.0.0-7.0.4 when AMQP protocols 0-8, 0-9 or
Unbounded echo flow responses in Apache Qpid Broker-J (all versions through 10.0.1) allow an authenticated AMQP 1.0 clie
Denial of service in Apache Qpid Broker-J through version 10.0.1 allows authenticated AMQP 1.0 clients to exhaust broker
EUVD-2026-86587
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB