IBM MQ is widely used enterprise messaging middleware; an authenticated RCE across many supported versions can disrupt services and enterprise operations.
CVE-2026-13292
Authenticated RCE in IBM MQ via malicious transfer metadata.
Is CVE-2026-13292 being exploited?
Not confirmed. CVE-2026-13292 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-13292?
CVE-2026-13292 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-13292?
Not known from our data. No patch reference has been recorded for CVE-2026-13292, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-13292 affect?
CVE-2026-13292 affects IBM MQ 9.2.0.0-9.2.0.44 LTS, IBM MQ 9.3.0.0-9.3.0.42 LTS, IBM MQ 9.4.0.0-9.4.0.26 LTS, IBM MQ 9.4.0.0-9.4.5.1 CD, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13292?
Apply vendor updates/mitigations when released; restrict MQ access and monitor transfer logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can inject environment variables in transfer request metadata to achieve remote code execution on MQ servers/processes.
Patch when possible
- affected>= 9.2.0.0 and <= 9.2.0.44
- affected>= 9.3.0.0 and <= 9.3.0.42
- affected>= 9.4.0.0 and <= 9.4.0.26
- affected>= 9.4.0.0 and <= 9.4.5.1
- affected>= 10.0.0.0 and <= 10.0.0.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
timeline
- 4 Nov 2026Published
- 4 Nov 2026CVE record last updated · same day later
- 5 Nov 2026Analysed by vulneraibility.com · same day later
- Patchibm.com /support/pages/node/7294641
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.