Live › vulnerability › CVE-2026-12670
Go to dashboardIBM MQ Operator can be driven into excessive memory use during character set conversion by a specially crafted message. An authenticated attacker can use this to cause a denial of service.
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 running the IBM MQ Operator on Kubernetes or OpenShift within the listed version ranges. Exposure requires an account that can send messages to the queue manager; the sources do not say whether unauthenticated access is possible. Teams on other IBM MQ versions or not running the Operator are not listed as 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 exact versions 3.3.0 through 3.6.2).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 denial of service through a specially crafted message that triggers excessive memory operations during character set conversion.
This page as .md · .json · in your agent: get_signal("CVE-2026-12670")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.