EUVD-2026-104464
GHSA-hp4q-fjfh-jhv7
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to IBM MQ with low privileges
-
ExploitSend crafted malformed compressed data
-
ImpactTrigger out-of-bounds read in decompressor (data not disclosed, request rejected)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection 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 IBM MQ connection (PR:L) capable of sending message data to an instance running the affected MQ Operator or MQ Advanced Container Images, and the payload must be malformed compressed data that reaches the decompression code path. Limiting factors: high attack complexity (AC:H) means the attacker must craft a specific malformed compressed structure; valid authentication/connection credentials are required (not remote-unauthenticated); the flaw is confined to the containerized/operator distributions per the listed CPEs; and the condition is self-limiting because the server rejects the malformed request and does not return the out-of-bounds data, so there is no actual data disclosure or service disruption. |
| Impact | This is a low-priority, high-CVSS-no it is a genuinely low-CVSS issue (3.1, LOW). The CVSS vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N indicates a network-reachable flaw but with high attack complexity (AC:H - crafting malformed compressed data that reaches the vulnerable parse path) and a requirement for existing low-level privileges (PR:L - an authenticated MQ client/connection). Impact is minimal: only a low confidentiality rating (C:L) with no integrity or availability impact, and the description itself states the out-of-bounds read does not disclose data and the request is rejected, so even the C:L rating overstates realistic consequence. No EPSS score, no CISA KEV listing, and no public exploit code are present in the provided data, so there is no public exploit identified at time of analysis. All signals are internally consistent and point to a benign, low-risk defect: an authenticated adversary can at most trigger a caught, non-disclosing memory read. There is a minor conflict worth noting - the input carries an 'Information Disclosure' tag and the CVSS assigns C:L, yet the description explicitly says data is NOT disclosed; verify the true confidentiality impact with IBM, as it may warrant C:N. This should be patched during normal maintenance, not treated as an emergency. |
| Exploit ScenarioDerived | An authenticated IBM MQ client connects to a containerized MQ instance (MQ Operator / Advanced Container Images) and sends a specially crafted, malformed compressed message payload. The server attempts to decompress it, performs a minor out-of-bounds read of adjacent memory, but the read value is not returned to the attacker and the malformed request is rejected. No public proof-of-concept exists, and the high attack complexity means a non-trivial crafted payload is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Malformed compressed message data delivered to containerized IBM MQ deployments (MQ Operator and MQ Advanced Container Images) can drive a minor out-of-bounds read (CWE-125) in the decompression code path, but the broker rejects the malformed request and does not return the over-read bytes, so no message or memory contents are exposed. The attacker must already hold valid MQ connection credentials (CVSS PR:L) and clear high attack complexity (AC:H) by crafting a specific malformed compressed structure, keeping the issue at CVSS 3.1 (Low). No public exploit code or active exploitation has been identified at time of analysis, and IBM has published a vendor fix via its support portal.
RemediationAI
Apply the vendor fix: IBM has released a patch for this issue and the corrected build levels are documented at https://www.ibm.com/support/pages/node/7292667 - upgrade the MQ Operator and any MQ Advanced Container Images deployments to the fixed image tags listed there (an exact fix version is not specified in the supplied data, so consult the advisory rather than assuming a version). Because exploitation requires an authenticated MQ connection, an effective interim control is to tighten who can send message data: enforce CHLAUTH channel authentication rules and restrictive MCAUSER mappings so only known applications can connect and publish, at the cost of administrative overhead and the risk of blocking legitimate publishers if rules are too broad. A second workaround is to disable message data compression on channels and topics where it is not required (COMPHDR/COMPMSG set to NONE), which keeps malformed compressed payloads out of the decompression routine entirely, at the cost of higher network bandwidth and CPU usage for large messages. Finally, alert on repeated malformed-message rejections and AMQ error codes on containerized queue managers, since failed decompression attempts are the observable footprint of an attempted trigger; this is detection only and does not remove the underlying read overflow.
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
The flaw is a classic out-of-bounds read (CWE-125) in the message decompression logic that IBM MQ applies when a client delivers compressed message data over an MQ connection. Decompression routines parse attacker-influenced header fields (compressed length, offsets, and block descriptors) before inflating the payload; when those fields are internally inconsistent, the routine advances a read pointer past the end of the allocated input buffer and reads a small number of adjacent bytes. Because the decompression fails and the broker rejects the request rather than returning the inflated output, the over-read stays internal - hence the Confidentiality-only, Low-severity scoring with no Integrity or Availability impact. Per the supplied CPEs, the affected distributions are the IBM MQ Operator and IBM MQ Advanced Container Images (wildcarded versions), i.e. the containerized/operator packaging of MQ rather than a discrete standalone server build, so exposure tracks whichever MQ image tag a deployment is running. Exploitation requires an authenticated session (PR:L per the CVSS vector) plus the ability to publish message data into the decompression path; there is no unauthenticated remote trigger and no denial-of-service component in the assessed vector.
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:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Network-reachable but requires an authenticated connection (PR:L) and a carefully crafted malformed compressed payload (AC:H); C:L retained per vendor though the non-disclosed, rejected read arguably justifies C:N.
Primary rating from Vendor (ibm).
CVSS VectorVendor: ibm
DescriptionCVE.org
IBM MQ could allow an authenticated attacker to trigger a minor out-of-bounds read when sending malformed compressed data, though the data is not disclosed and the request is rejected.
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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,
Denial of service in IBM MQ Operator and IBM MQ Advanced container images lets an authenticated MQ client crash the queu
Authenticated denial of service in IBM MQ container deployments - specifically the MQ Operator and MQ Advanced container
Exploit-DB