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
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 4 Nov 2026, 22:37 UTC
Thin evidence
One scorer or none| CNA (ibm) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| IBMMQ Appliance | Affected
| Fixed in– |
AI-suggested
Until a fix is available, organizations should restrict authenticated access to IBM MQ instances to trusted users only and monitor for unusual activity related to message header processing.
Description
IBM MQ versions 9.4.0.0 through 9.4.0.26, 9.4.1.0 through 9.4.5.3, and 10.0.0.1 through 10.0.0.5 contain a vulnerability where improper validation of message header structure length fields could allow an authenticated attacker to obtain sensitive information or cause a denial of service.