Skip to main content

IBM MQ EUVDEUVD-2026-83021

| CVE-2026-10751 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-09-18 ibm GHSA-94jh-fv89-qhj3
7.5
CVSS 3.1 · Vendor: ibm
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to MQ or control a consumed queue
  2. Delivery
    Deliver crafted serialized objects into message flow
  3. Exploit
    Client hits exception-handling deserialization path
  4. Execution
    Filter bypass instantiates gadget chain
  5. Impact
    Arbitrary code executes in client process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the IBM MQ Java or JMS client libraries to be in use by a consuming application. The attacker needs authenticated access to MQ (PR:L) or control over a queue/topic/message source the victim client reads, so that attacker-controlled serialized data reaches the client. Exploitation is limited to the specific exception-handling code path where the deserialization allow-list filter is bypassed (reflected by AC:H), and impact is confined to the client application process rather than the MQ server. No user interaction is required (UI:N). The vulnerable component is the client library, so server-only deployments without affected Java/JMS clients are not exposed.

Impact

The vendor CVSS 3.1 vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.5 High) reflects a network-reachable but non-trivial code-execution flaw requiring authentication. Several signals temper the raw score: AC:H indicates the deserialization-filter bypass triggers only along a specific exception-handling path rather than trivially, and PR:L means the attacker must be an authenticated MQ participant, not an anonymous internet actor. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so exploitation is not yet demonstrated: no public exploit identified at time of analysis. A key nuance is that the impact lands on the CLIENT application, not the MQ server - so 'network attack vector' here typically means a malicious or compromised message/queue source feeds crafted serialized data back to the Java/JMS client, inverting the usual server-target threat model. Net: a credible, patch-worthy High for organizations running IBM MQ Java/JMS clients, but not an emergency-grade, mass-exploited priority given AC:H, PR:L, absent EPSS/KEV/POC, and the client-side (rather than server-side) blast radius.

Exploit ScenarioDerived

An attacker with valid MQ credentials (or control of a queue/topic a victim client consumes from) places crafted serialized Java objects that, when the client library encounters an error and enters its exception-handling deserialization path, bypass the object-input allow-list filter and instantiate attacker-chosen gadget classes. When the victim Java/JMS client application processes the message, arbitrary code executes in the client process. No public exploit code was provided, and the AC:H rating reflects that reaching the vulnerable exception path requires specific conditions.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 18, 2026

Remote code execution in IBM MQ Java and JMS client libraries allows an authenticated attacker with access to a message queue or topic to bypass the deserialization allow-list filter in exception handling and execute arbitrary code on client applications. The flaw is network-reachable but requires low-privileged authentication (PR:L) and is limited to a specific exception-handling path (AC:H), with impact confined to the client process rather than the MQ server. No public exploit code was identified at time of analysis.

RemediationAI

Apply the vendor-released patch available from IBM (see advisory https://www.ibm.com/support/pages/node/7284898 for the exact fix version and instructions). As a compensating control, restrict authenticated access to MQ so that only trusted principals can send messages to queues or topics consumed by Java/JMS clients; however, this may impact legitimate messaging workflows and does not fully eliminate the risk if an attacker gains such access. Additionally, consider implementing a custom deserialization filter on the client side to block unexpected classes, but be aware that the bypass in exception handling may render such filters ineffective in this specific code path. Monitor client applications for signs of deserialization attacks and review IBM's advisory for any updated mitigations.

Affected VersionsENISA

MQ 9.1.0.0 ≤9.1.0.37 LTS
MQ 9.4.0.0 ≤9.4.0.25 LTS
MQ 10.0.0.0
MQ 9.4.0.0 ≤9.4.5.1 CD
MQ 9.3.0.0 ≤9.3.0.41 LTS
MQ 9.2.0.0 ≤9.2.0.43 LTS
MQ 9.3.0.0 ≤9.3.5.1 CD

Affected Packages

euvd mq no fix

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

The vulnerability is a CWE-502 deserialization of untrusted data issue in the Java and JMS client libraries of IBM MQ. When the client processes a message that triggers an exception, the deserialization allow-list filter can be bypassed, allowing attacker-controlled serialized data to be deserialized without proper validation. This can lead to arbitrary code execution in the context of the client application. The attack requires the attacker to have authenticated access to MQ (PR:L) or control over a queue/topic/message source that the victim client reads, so that crafted serialized data reaches the vulnerable exception-handling code path. The network vector (AV:N) and high attack complexity (AC:H) reflect that exploitation is non-trivial and confined to the client library process, not the MQ server. The CPE cpe:2.3:a:ibm:mq:*:*:*:*:*:*:*:* indicates all versions are potentially affected, though specific version ranges should be confirmed in the IBM advisory.

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

Vendor (ibm) PRIMARY 7.5 HIGH
AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

Network-delivered crafted objects (AV:N) reach a specific exception path (AC:H) requiring authenticated MQ access (PR:L); code execution on the client yields full C:H/I:H/A:H with no scope change.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

IBM MQ Java and JMS client libraries could allow an authenticated attacker to execute arbitrary code on client applications due to a deserialization filter bypass in exception handling.

Executive ViewAI

Why It Matters

IBM MQ Java and JMS client libraries sit inside the business applications that consume messages from enterprise queues, and CVE-2026-10751 lets an attacker run arbitrary code within those client processes rather than on the MQ server itself. Exploitation requires only low-privileged, authenticated access to a queue or topic and is confined to a specific exception-handling path, so the practical exposure concentrates in organizations where many internal applications share messaging infrastructure and queue permissions are broadly granted. Leadership should treat this as an integration-layer risk: a single compromised client process can serve as a foothold for lateral movement and can disrupt transaction and batch workloads that depend on reliable messaging.

Business Impact: High
Compensating Controls

Apply vendor patch. Until patched clients are deployed, restrict publish and subscribe permissions on affected queues and topics to the minimum set of trusted service identities, monitor client processes for unexpected child processes or outbound connections, and prioritize patching clients that consume messages from sources outside the direct control of the application owner.

Threat Intelligence Overview

EPSS Score
0.5%
Top 58% exploitable
Prevalence
High
IBM MQ is widely deployed enterprise messaging middleware with common Java/JMS clients
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in Mq

View all
CVE-2026-12351 CRITICAL
9.8 Sep 15

Remote code execution in IBM MQ is possible when the optional IVT (Installation Verification Test) application is deploy

CVE-2026-10027 CRITICAL
9.8 Sep 18

Malformed compressed data delivered over an IBM MQ channel that has compression enabled can trigger an out-of-bounds hea

CVE-2022-22489 CRITICAL
9.1 Aug 19

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

CVE-2026-11375 HIGH
8.8 Sep 18

IBM MQ queue managers that process XA (X/Open distributed) transactions are vulnerable to a memory-corruption buffer ove

CVE-2026-11378 HIGH
8.8 Sep 18

Integer overflow (CWE-190) in IBM MQ distribution list processing lets an authenticated user with PUT authority to a dis

CVE-2026-12728 HIGH
8.8 Sep 15

Authenticated remote code execution in IBM MQ lets an attacker who holds valid MQ credentials - or who can reach a chann

CVE-2026-10575 HIGH
8.8 Sep 18

Heap-based buffer overflow in IBM MQ allows an authenticated, low-privilege attacker who can reach a queue manager to ca

CVE-2026-11725 HIGH
8.8 Sep 18

An integer overflow in IBM MQ's MQINQ (inquire object attributes) request processing lets an authenticated remote user c

CVE-2026-10853 HIGH
8.8 Sep 18

IBM MQ queue managers running affected releases can be crashed - and, per IBM, potentially have arbitrary code executed

CVE-2024-31912 HIGH
8.8 Jun 28

IBM MQ 9.3 LTS and 9.3 CD could allow an authenticated user to escalate their privileges under certain configurations du

CVE-2026-11729 HIGH
8.5 Sep 15

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

CVE-2026-11728 HIGH
8.1 Sep 15

A heap buffer overflow in the IBM MQ client (CWE-787) can be triggered when the client processes crafted messages delive

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy