Live › vulnerability › CVE-2026-11831
Go to dashboardAn out-of-bounds read in IBM MQ Operator lets an authenticated client send a crafted request that causes a limited denial of service. The same flaw reveals very limited information about process memory layout.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams that run IBM MQ Operator in the affected version ranges and accept client connections from authenticated users. Exposure depends on who can send requests to the queue manager, so teams with no authenticated client access have less reason to worry. The sources do not say whether the default configuration is affected.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| ibm mq operator | vendor | >= 2.0.0, <= 2.0.29 | – |
| ibm mq operator | vendor | >= 3.2.0, <= 3.2.29 | – |
| ibm mq operator | vendor | = 3.3.0 | – |
| ibm mq operator | vendor | = 3.4.0 | – |
| ibm mq operator | vendor | = 3.4.1 | – |
| ibm mq operator | vendor | = 3.5.0 | – |
| ibm mq operator | vendor | = 3.5.1 | – |
| ibm mq operator | vendor | = 3.5.2 | – |
| ibm mq operator | vendor | = 3.5.3 | – |
| ibm mq operator | vendor | = 3.6.0 | – |
| ibm mq operator | vendor | = 3.6.1 | – |
| ibm mq operator | vendor | = 3.6.2 | – |
| ibm mq operator | vendor | = 3.6.3 | – |
| ibm mq operator | vendor | = 3.6.4 | – |
| ibm mq operator | vendor | = 3.7.0 | – |
| ibm mq operator | vendor | = 3.7.1 | – |
| ibm mq operator | vendor | = 3.7.2 | – |
| ibm mq operator | vendor | = 3.8.0 | – |
| ibm mq operator | vendor | = 3.8.1 | – |
| ibm mq operator | vendor | = 3.9.0 | – |
| ibm mq operator | vendor | = 3.9.1 | – |
| ibm mq operator | vendor | = 3.9.2 | – |
| ibm mq operator | vendor | = 4.0.0 | – |
| ibm mq operator | vendor | = 4.0.1 | – |
| ibm mq operator | vendor | = 4.0.2 | – |
| ibm mq operator | vendor | = 4.0.3 | – |
| ibm mq operator | vendor | = 4.0.4 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.1.0 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.1.1 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.2.0 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.2.1 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.3.0 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.3.1 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.4.0 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.4.1 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.5.0 | – |
| ibm supplied mq advanced container images | vendor | = 9.4.5.1 | – |
| ibm supplied mq advanced container images | vendor | = 10.0.0.0 | – |
| ibm supplied mq advanced container images | vendor | = 10.0.0.5 | – |
| ibm supplied mq advanced container images | vendor | = 9.3.0.0 | – |
2.0.0 to 2.0.29, 3.2.0 to 3.2.29, and exactly 3.3.0, 3.4.0, 3.4.1, 3.5.0 to 3.5.3, 3.6.0 to 3.6.2.kubectl get csv in the operator namespace), if the team runs it on Kubernetes.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
IBM MQ could allow an authenticated attacker to cause a limited denial of service and obtain very limited information about process memory layout due to an out-of-bounds read when processing a specially crafted client request.
This page as .md · .json · in your agent: get_signal("CVE-2026-11831")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.