CVE-2026-11728: IBM MQ .NET client is vulnerable to remote code execution

Published Sep 14, 2026
·
Updated

IBM MQ .NET Client could allow a remote attacker to cause a denial of service or potentially execute arbitrary code in the client due to a heap buffer overflow when receiving messages from a malicious queue manager or through a man-in-the-middle attack.

Other sources

IBM MQ 9.1.0.0 through 9.1.0.37 LTS, 9.2.0.0 through 9.2.0.43 LTS, 9.3.0.0 through 9.3.0.41 LTS, 9.3.0.0 through 9.3.5.1 CD, 9.4.0.0 through 9.4.0.25 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 could allow a remote attacker to cause a denial of service or potentially execute arbitrary code in the client due to a heap buffer overflow when receiving messages from a malicious queue manager or through a man-in-the-middle attack.

MITRE

Affected Software

7 affected components
IBM MQ<=9.1.0.0 to 9.1.0.37 LTS
IBM MQ<=9.2.0.0 to 9.2.0.43 LTS
IBM MQ<=9.3.0.0 to 9.3.0.41 LTS
IBM MQ<=9.3.0.0 to 9.3.5.1 CD
IBM MQ<=9.4.0.0 to 9.4.0.25 LTS
IBM MQ<=9.4.0.0 to 9.4.5.1 CD
IBM MQ<=10.0.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade IBM MQ .NET Client to a version that resolves this vulnerability.

    Fixed in 9.1.0.38
  2. Upgrade

    Upgrade IBM MQ .NET Client to a version that resolves this vulnerability.

    Fixed in 9.2.0.44
  3. Upgrade

    Upgrade IBM MQ .NET Client to a version that resolves this vulnerability.

    Fixed in 9.3.0.42
  4. Upgrade

    Upgrade IBM MQ .NET Client to a version that resolves this vulnerability.

    Fixed in 9.4.0.26
  5. Upgrade

    Upgrade IBM MQ .NET Client to a version that resolves this vulnerability.

    Fixed in 10.0.0.5
  6. Compensating control

    If applicable and before the upgrade, mitigate exposure by preventing connections to untrusted/malicious queue managers and avoiding man-in-the-middle risk (e.g., ensure secure client/queue manager communication).

  7. Operational

    After upgrading IBM MQ .NET Client (and related IBM MQ components as needed), restart affected client applications to ensure the updated client libraries are in use.

Event History

Sep 14, 2026
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Sep 15, 2026
CVE Published
via MITRE·05:42 PM
Data Sourced
via MITRE·05:42 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using the IBM MQ .NET Client in the listed IBM MQ 9.1, 9.2, 9.3, 9.4, or 10.0.0.0 versions are exposed when the client receives messages from a malicious queue manager or an attacker can perform a man-in-the-middle attack.

2

What does an attacker need to exploit the vulnerability?

An attacker must be able to send malicious messages through a malicious queue manager or intercept and modify traffic between the client and queue manager. No privileges or user interaction are required according to the supplied severity vector.

3

What is the potential impact on an affected client?

Successful exploitation may cause a denial of service or potentially allow arbitrary code execution on the system running the IBM MQ .NET Client.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203