GHSA-638c-6pmf-jwmg
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach broker AMQP 0-10 port
-
DeliverySend crafted frame with oversized type/count
-
ExploitDecoder attempts excessive allocation
-
ExecutionJVM heap exhaustion
-
ImpactBroker crash/hang denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to a broker running the AMQP 0-10 protocol plugin (org.apache.qpid:qpid-broker-plugins-amqp-0-10-protocol) at version 10.1.0 or earlier; the attacker crafts frames with malicious type size/count values that the 0-10 decoder processes before authentication. No credentials, user interaction, or non-default authentication is needed - the vulnerable code path is reached pre-authentication. Limiting factors: the AMQP 0-10 protocol handler must be enabled and the broker's AMQP port must be exposed to the attacker; deployments that only enable AMQP 1.0/0-9-1 or restrict network access to the broker are correspondingly less exposed. Impact is limited to availability (broker DoS) with no data exposure or modification. |
| Impact | This is a pre-authentication denial-of-service via uncontrolled memory allocation (type size/count mishandling) in the AMQP 0-10 protocol decoder of Apache Qpid Broker-J through 10.1.0. No NVD CVSS vector, CWE, EPSS score, KEV entry, or public exploit was provided, so raw prioritization signals are largely absent - the only severity anchor is Apache's own rating of 'important'. My independent assessment places this at CVSS 3.1 ~7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H): the flaw is remotely reachable before authentication over the AMQP protocol port, which is the aggravating factor, but the impact is confined to availability (crash/OOM) with no confidentiality or integrity loss. Net real-world risk is moderate rather than critical: the pre-auth network reach makes it easy to trigger against any exposed broker, yet the single-impact DoS ceiling and the niche footprint of a pure-Java AMQP broker cap the blast radius. Exploitation status is 'no public exploit identified at time of analysis' - absence of EPSS/KEV/POC data means widespread opportunistic exploitation cannot be inferred; treat as a patch-soon issue for internet-exposed brokers rather than an emergency. Note: no machine-readable CVSS was supplied by NVD or the vendor, so the vector above is analyst-derived and should be verified against the eventual NVD/CNA record. |
| Exploit ScenarioDerived | An attacker who can reach the broker's AMQP 0-10 listener sends a crafted protocol frame with manipulated type size or element-count fields before completing authentication. The decoder trusts these values and attempts an excessive memory allocation, exhausting the JVM heap and crashing or hanging the broker, denying messaging service to all legitimate clients. No public exploit code was identified at time of analysis. |
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: a remote attacker who can reach a broker with the AMQP 0-10 protocol plugin enabled can send frames whose type size and count fields are not properly bounded, driving the decoder into excessive memory allocation and potentially exhausting broker resources. The affected code path is reached before authentication (assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so no credentials or user interaction are required; impact is limited to availability, with no confidentiality or integrity effect. There is no public exploit code identified at time of analysis and no confirmed active exploitation (not in CISA KEV); a vendor-released fix exists in version 10.1.1.
RemediationAI
Vendor-released patch: upgrade Apache Qpid Broker-J to version 10.1.1, which fixes the type size/count handling in the AMQP 0-10 decoder; this is the primary and preferred action, and no CVSS vector or patch workaround was published by the vendor beyond the version bump. If an immediate upgrade is not possible, reduce exposure by removing or disabling the AMQP 0-10 protocol plugin (org.apache.qpid:qpid-broker-plugins-amqp-0-10-protocol) from the broker configuration so the vulnerable decoder is never instantiated - the trade-off is that any clients still speaking AMQP 0-10 will fail to connect, so confirm client protocol usage first. As a secondary control, restrict network access to the broker's AMQP listener with firewall rules or bind the port to trusted interfaces/VPN only, which limits the attack surface to trusted peers at the cost of blocking legitimate remote producers and consumers. Monitor broker JVM heap, GC pressure, and out-of-memory events as detection signals, and restart or throttle offending connections if memory growth is observed. Consult https://qpid.apache.org/ and the advisory at https://seclists.org/oss-sec/2026/q3/928 for any further vendor guidance; there is no indication of a downstream backport list in the available data.
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, and the vulnerable component is the AMQP 0-10 protocol plugin (org.apache.qpid:qpid-broker-plugins-amqp-0-10-protocol), a legacy dialect of AMQP that predates the widely deployed 0-9-1 and 1.0 versions. The flaw lies in the decoder's handling of type size and count values inside incoming frames: the decoder reads attacker-controlled lengths/counts and allocates buffers or collections based on them without adequate validation against the actual frame size or configured limits (the resource-exhaustion class commonly described as CWE-770/789, though no CWE was recorded in the advisory data). Because decoding of the protocol header and frame types occurs during connection setup, before any SASL/authentication exchange completes, the allocation is triggered pre-authentication, giving an unauthenticated network attacker a direct path to a memory pressure or out-of-memory condition on the JVM. Exposure is conditional on the AMQP 0-10 handler actually being enabled and the broker's AMQP listener being reachable from the attacker's network position.
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 (PR:N) network-reachable (AV:N) AMQP frame triggers excessive allocation with low complexity (AC:L); impact is availability-only DoS (C:N/I:N/A:H).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Description PRE-NVD
Articles & Coverage 1
Executive ViewAI
A pre-authentication denial-of-service flaw in Apache Qpid Broker-J (versions through 10.1.0) lets anyone who can reach a broker with the AMQP 0-10 protocol plugin enabled exhaust its memory and take it offline. Because the assessed vector is network-reachable and requires no credentials or user interaction, any internet- or partner-facing broker with that plugin enabled is exposed to outage on demand. Leadership should care because the consequence is service disruption, not data theft - confidentiality and integrity are unaffected - yet an outage of a shared broker can cascade across every application, integration, and event pipeline that depends on it.
Apply vendor patch (Qpid Broker-J 10.1.1; confirm against the vendor advisory, since the structured patch field reports none available). Where the upgrade cannot be completed immediately: disable the AMQP 0-10 protocol plugin on any broker that does not require it, restrict the AMQP 0-10 listener to trusted networks via firewall or security-group rules, cap broker memory/heap and connection limits to bound the impact of excessive decoder allocation, and monitor broker memory and connection metrics for anomalous spikes.
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) allows a remote attacker to exhaust broker
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-86586
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB