EUVD-2026-104472
GHSA-r558-qrg5-2jq5
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid MQ client credentials
-
DeliveryConnect to target queue manager
-
ExploitSend MQOPEN with malformed offset
-
ExecutionTrigger buffer-handling fault
-
ImpactDenial of service on messaging
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to be an authenticated IBM MQ client (PR:L) with an established connection to the target queue manager, able to issue MQOPEN API calls - this is the core limiting factor and rules out anonymous internet-wide abuse. The specific trigger is an MQOPEN request carrying an offset value that the queue manager fails to validate properly; no special non-default feature toggle is named in the description, so default configurations that accept authenticated MQOPEN calls appear affected. Affected deployments are specifically the IBM MQ Operator and MQ Advanced container images (Kubernetes/OpenShift-style containerized MQ) per the CPE data, not necessarily traditional installed MQ builds. No user interaction is required (UI:N), but valid MQ credentials are mandatory, which confines realistic risk to insiders or attackers who have already compromised an MQ application identity. |
| Impact | This is a moderate, not top-tier, priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 6.5) describes a network-reachable, low-complexity availability-only flaw that requires an authenticated attacker (PR:L), so there is no confidentiality or integrity impact - only denial of service. All exploitation signals point AWAY from active threat: there is no CISA KEV listing, no public exploit code, and CISA's SSVC decision framework explicitly rates Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial'. No EPSS score was provided in the input, so the empirical exploitation-probability signal is MISSING and cannot be weighed. The CWE is listed as CWE-120 (buffer overflow / improper offset validation in MQOPEN), consistent with the description, but the manifestation here is a crash/DoS rather than code execution. The principal limiting factor is the PR:L requirement: an attacker must already hold valid MQ credentials (a connected, authenticated application/queue-manager session) to send the malformed MQOPEN request, which substantially narrows the realistic threat to insiders or attackers who have already obtained MQ client credentials. Net: a genuine but contained availability risk for authenticated clients, worth patching on a normal enterprise cadence rather than as an emergency. |
| Exploit ScenarioDerived | An attacker with valid IBM MQ client credentials connects to a queue manager and sends an MQOPEN request containing a crafted, out-of-range offset value that bypasses proper validation, causing a buffer-handling fault that disrupts or crashes message processing. No public proof-of-concept or exploit code has been identified, and the attacker gains no data access or code execution - only a denial of service against the messaging service. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Denial of service in IBM MQ Operator and IBM MQ Advanced container images lets an authenticated MQ client crash the queue manager by sending an MQOPEN request whose offset values are not properly validated, producing a buffer-handling fault in the queue manager process. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) shows the limiting factor is credentials: the attacker must already hold a valid MQ identity and an established connection able to issue MQ API calls, so exposure is limited to insiders or attackers who have compromised an MQ application identity. Confidentiality and integrity are unaffected, the vendor has published a fix, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none, automatable: no).
RemediationAI
Apply the vendor fix documented in IBM support advisory https://www.ibm.com/support/pages/node/7292667 - the patch is available from the vendor, and containerized deployments should be moved to the corrected MQ Advanced container image tag / MQ Operator release listed there and rolled out with a queue manager restart (the exact fixed version is not specified in the provided data, so confirm the target image digest against the advisory before upgrading). Until upgrades complete, the most effective compensating control is to restrict who can reach the queue manager's MQI listeners: enforce CHLAUTH channel authentication rules and TLS-only SVRCONN channels so only named user IDs and trusted network ranges can connect, which shrinks the population able to send a malicious MQOPEN but will break any unlisted application identities. Tighten object authority with setmqaut so each application identity can open only the queues it actually needs, which limits reachable MQOPEN targets and contains the blast radius if one identity is compromised, at the cost of administrative overhead and possible application failures if authority is under-granted. Segment MQ listener ports behind network policy so only application namespaces can connect, and monitor the queue manager for abnormal termination, FDC/FFST dumps, and repeated MQOPEN errors from a single connection as a detection signal for a crash attempt; these reduce exposure but do not remediate the underlying defect, and none of them protect against an already-trusted insider identity.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages 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 a message-oriented middleware queue manager, and MQOPEN is the core Message Queue Interface (MQI) verb a client or binding application issues to open a queue (or other object) before putting or getting messages; the request carries object descriptor and connection structures with position/offset fields that the queue manager must range-check. CVE-2026-11829 is classified as CWE-120 (buffer copy without checking size of input, the classic unchecked buffer copy), which indicates that a crafted offset value in an MQOPEN request causes data to be copied or indexed outside the bounds of an internal buffer rather than being rejected as invalid input. The result is a fault in the queue manager rather than memory-corruption-driven code execution, matching the assessed impact of availability-only (A:H) with no confidentiality or integrity effect. The affected CPE entries are the containerized delivery vehicles - IBM MQ Operator and IBM MQ Advanced container images, both matched with wildcard versions - which is consistent with a defect in the queue manager code shipped inside those images; the provided data does not establish that traditional standalone on-premises MQ installations are affected. Because no non-default feature toggle is identified, default configurations that accept authenticated MQOPEN calls appear in scope, and no user interaction is required (UI:N).
Know when Mq Operator 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 MQOPEN call with low complexity but requires valid MQ client authentication (PR:L); availability-only crash, so C:N/I:N/A:H and scope unchanged.
Primary rating from Vendor (ibm).
CVSS VectorNVD
DescriptionNVD
IBM MQ could allow an authenticated attacker to cause a denial of service due to improper validation of offset values in MQOPEN requests.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
More in Mq Operator
View allIBM MQ Operator 3.2.2 and IBM MQ Operator 2.0.24 could allow a user to bypass authentication under certain configuration
Heap buffer overflow in IBM MQ Operator and IBM MQ Advanced Container Images lets an authenticated user with authority t
Denial of service and potential remote code execution in IBM MQ deployments using the MQ Operator and MQ Advanced Contai
Authenticated users of containerized IBM MQ deployments can cause denial of service or memory corruption by sending MQOP
IBM MQ 9.1 LTS, 9.2 LTS, 9.3 LTS, 9.3 CD, 9.4 LTS, and 9.4 CD could allow an authenticated user in a specifically define
Unauthenticated remote code execution is possible against IBM MQ deployments exposed through the MQ Operator and MQ Adva
Authenticated attackers with access to IBM MQ Operator or MQ Advanced Container Images deployments can exploit unrestric
IBM MQ Operator 3.2.2 and IBM MQ Operator 2.0.24 IBM MQ Container Developer Edition is vulnerable to denial of service c
IBM MQ Operator 2.0.0 LTS, 2.0.18 LTS, 3.0.0 CD, 3.0.1 CD, 2.4.0 through 2.4.7, 2.3.0 through 2.3.3, 2.2.0 through 2.2.2
IBM MQ Operator LTS 2.0.0 through 2.0.29, MQ Operator CD 3.0.0, 3.0.1, 3.1.0 through 3.1.3, 3.3.0, 3.4.0, 3.4.1, 3.5.0,
Authenticated denial of service in IBM MQ container deployments - specifically the MQ Operator and MQ Advanced container
Authenticated users of IBM MQ Operator and IBM MQ Advanced container image deployments can cause a denial of service aga
Exploit-DB