IBM MQ (.NET MESSAGING / XMS .NET CLIENT) · CVE-2026-10859 · Runtime
FIX → 9.2.0.46 · 9.3.0.43 · 9.4.0.30 · 10.0.0.6 ✓ verified
IBM's bulletin says the IBM MQ XMS .NET client (the .NET messaging component of IBM MQ) insecurely deserializes ObjectMessage payloads, so an authenticated attacker could execute arbitrary code in consumer applications. IBM lists no workarounds.
first public Nov 4, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running IBM MQ with the .NET messaging (XMS .NET client) component, whose .NET consumer applications read ObjectMessage payloads. The attacker needs valid credentials to the messaging system, and IBM rates attack complexity high. Sites without the .NET messaging component or without ObjectMessage consumers can likely skip it; IBM does not state this explicitly.
Not affected if auth-required, no-dotnet-messaging-component, no-objectmessage-consumers
Who cares deserialization, dotnet, ibm-mq, java, messaging, xms
IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD could allow an authenticated attacker to execute arbitrary code on consumer applications due to insecure deserialization of ObjectMessage payloads.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 9.2.0.46 · 9.3.0.43 · 9.4.0.30 · 10.0.0.6
Apply IBM's fixes: 9.2 LTS cumulative security update 9.2.0.46; 9.3 LTS 9.3.0.43; 9.4 LTS fix pack 9.4.0.30; 10.0 LTS upgrade to 10.0.0.6; 9.4 CD and 10.0 CD upgrade to 10.0.1.0 (Known Issue DT472703).