CVE-2026-12538 · Runtime
NO FIX YET · SEE WHAT TO DO
IBM MQ does not properly validate the length fields in message header structures. An authenticated attacker can read sensitive information or cause a denial of service.
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 that run IBM MQ 9.4.0.0 to 9.4.0.26, 9.4.1.0 to 9.4.5.3, or 10.0.0.1 to 10.0.0.5 are exposed. The attacker must hold valid credentials to an MQ connection. Systems on other MQ versions, or with no MQ installed, can skip it.
Not affected if no-mq-installed, unaffected-version
Who cares ibm-mq, messaging, self-hosted
dspmqver and compare it with the affected ranges: 9.4.0.0 to 9.4.0.26, 9.4.1.0 to 9.4.5.3, and 10.0.0.1 to 10.0.0.5.IBM MQ 9.4.0.0 to 9.4.0.26, 9.4.1.0 to 9.4.5.3, and 10.0.0.1 to 10.0.0.5 could allow an authenticated attacker to obtain sensitive information or cause a denial of service due to improper validation of message header structure length fields.
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.