CVE-2026-12550 · Package
NO FIX YET
IBM MQ does not properly validate message selection parameters, so a logged-in user can read sensitive information or trigger a denial of service. The sources list affected releases across MQ 9.2, 9.3, 9.4 and 10.0 but do not describe the exact leak.
first public Nov 4, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running IBM MQ message brokers within the listed version ranges are exposed, and the attacker must already hold valid MQ credentials. Systems on versions outside these ranges, or without any MQ deployment, can skip it. The sources do not describe a specific non-default configuration.
Not affected if no-mq-deployment, version-outside-range
Who cares ibm-mq, messaging, self-hosted
dspmqver on each queue manager host and compare it to the affected ranges.No fix yet, per the sources.
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 obtain sensitive information or cause a denial of service due to improper validation of message selection parameters.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L
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.