Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid MQ credentials
-
DeliveryConnect to queue manager and target queue
-
ExploitPut specially crafted message
-
ExecutionConsuming application processes malformed message
-
ImpactApplication crash denies 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 an authenticated MQ user (PR:L) with authority to put messages onto a queue that is read by a vulnerable consuming application, and the targeted deployment must run an affected version (IBM MQ 9.4.5.0 through 9.4.5.1). The attack is network-reachable (AV:N) with low complexity (AC:L) and needs no user interaction (UI:N). Limiting factors: valid credentials and put-authority on the relevant queue are mandatory, so the flaw is not exploitable by fully unauthenticated attackers; impact is confined to availability (crash of the consuming application) with no confidentiality or integrity effect, and versions outside the 9.4.5.0-9.4.5.1 range are not affected. |
| Impact | This is a medium-severity, authenticated denial-of-service issue that should be prioritized as routine patch-management rather than emergency response. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 6.5) indicates a network-reachable, low-complexity attack but one that requires valid, low-level credentials (PR:L) and yields only availability impact - no confidentiality or integrity loss. No EPSS score, CISA KEV listing, or public proof-of-concept was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The practical risk is bounded by the authentication requirement: an attacker must already be an authorized MQ user able to put messages onto a queue that a vulnerable consuming application reads. Because MQ is widely used as core enterprise messaging middleware, the blast radius of a crashed consumer can be operationally significant, but the signals are internally consistent (network vector with low-privilege auth, availability-only impact) and point to an insider- or compromised-credential threat model rather than a wormable, unauthenticated internet-facing flaw. No key signals conflict; the main missing data are EPSS/KEV/POC, whose absence lowers urgency but does not eliminate the need to patch. |
| Exploit ScenarioDerived | An authenticated MQ user (or an attacker who has obtained valid MQ credentials) with permission to put messages on a queue sends a single specially crafted message to a queue serviced by a downstream consuming application. When the application dequeues and processes the malformed message, it crashes, interrupting the business process that depends on it. No public exploit code was identified, and exploitation requires only low privileges and low attack complexity per the CVSS vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Crafted messages published into IBM MQ 9.4.5.0 or 9.4.5.1 can crash the applications that consume them, giving an authenticated message producer a denial-of-service primitive against queue-processing services. Successful exploitation requires a valid MQ identity with put authority on a queue that a vulnerable consumer reads; the CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, score 6.5) confirms the attacker must be authenticated and that only availability is impacted, with no confidentiality or integrity effect. There is no CISA KEV listing and no public exploit identified at time of analysis, so this should be handled as routine, medium-severity patch management rather than emergency response, especially since deployments outside the 9.4.5.0-9.4.5.1 range are not affected.
RemediationAI
Patch status is vendor-confirmed: IBM has published a fix for this defect in its support bulletin at https://www.ibm.com/support/pages/node/7290859, and the action is to upgrade IBM MQ off the 9.4.5.0-9.4.5.1 levels to the fixed maintenance level IBM identifies in that advisory (the input data does not state the exact fix version, so confirm it in the bulletin before scheduling the upgrade, and apply it to queue managers as well as any consumer-side MQ client libraries in use). Where the upgrade cannot be applied immediately, reduce exposure by restricting put authority on queues consumed by business-critical applications to the specific, trusted producer user IDs using MQ authority records (setmqaut) rather than broad group grants, which removes the primitive from all but a small set of identities at the cost of possibly breaking existing integrations that relied on permissive grants; and by tightening channel authentication records (CHLAUTH) with BLOCKUSER rules and explicit MCAUSER mappings so that only strongly identified connections can place messages. Enforce conservative MAXMSGL and queue-depth limits and alert on consumer restarts to catch exploitation attempts early, accepting that these limits may reject legitimately large messages. Because exploitation crashes the consuming application rather than the queue manager, deploying restart supervision or high-availability for consumers limits outage duration but does not remove the underlying defect, so treat these as temporary measures until the vendor fix is installed.
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
IBM MQ is enterprise message-oriented middleware in which queue managers host queues, and producers put messages that consumer applications retrieve and process; authorization to put messages is governed per-queue through MQ authority records and channel-side identity mapping (CHLAUTH/MCAUSER). The flaw is classified as CWE-770 (Allocation of Resources Without Limits or Throttling), meaning the message-handling path does not bound or validate the resources a single crafted message can demand, so a malformed or adversarial payload reaches the consuming application and terminates it rather than being rejected or throttled cleanly. The generic CPE cpe:2.3:a:ibm:mq:*:*:*:*:*:*:*:* matches the product family broadly, but per IBM only the 9.4.5.0 through 9.4.5.1 maintenance levels contain the defect. Note the boundary of the issue: the queue manager itself is not described as compromised, confidentiality and integrity are unaffected, and the prerequisite of an authenticated producer with put authority on the target queue substantially narrows the attacker population compared with an unauthenticated network flaw.
Know when Mq 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:L/UI:N/S:U/C:N/I:N/A:H
Network-reachable messaging requires valid low-privilege MQ credentials (PR:L) and no interaction; impact is availability-only (A:H) from the consumer crash, with no C or I loss.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM MQ 9.4.5.0 through 9.4.5.1 could allow an authenticated user to cause a denial of service by sending a specially crafted message that crashes consuming applications.
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.
Remote code execution in IBM MQ is possible when the optional IVT (Installation Verification Test) application is deploy
Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds hea
IBM MQ 8.0, (9.0, 9.1, 9.2 LTS), and (9.1 and 9.2 CD) are vulnerable to an XML External Entity Injection (XXE) attack wh
IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer ove
Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a dis
Authenticated remote code execution in IBM MQ lets an attacker who holds valid MQ credentials - or who can reach a chann
Heap-based buffer overflow in IBM MQ allows an authenticated, low-privilege attacker who can reach a queue manager to ca
An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user c
IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed
IBM MQ 9.3 LTS and 9.3 CD could allow an authenticated user to escalate their privileges under certain configurations du
Unsafe Java object deserialization in IBM MQ (9.1.0.0-9.1.0.37 LTS, 9.2.0.0-9.2.0.43 LTS, 9.3.0.0-9.3.0.41 LTS / 9.3.0.0
A heap buffer overflow in the IBM MQ client (CWE-787) can be triggered when the client processes crafted messages delive
EUVD-2026-104477
GHSA-frv9-r4g5-6cvx
NVD
CVE.org
EPSS
Exploit-DB