RCE in widely used enterprise middleware (IBM MQ) that can lead to host compromise across organizations.
CVE-2026-13293
Authenticated remote code execution in IBM MQ via unsafe deserialization.
Is CVE-2026-13293 being exploited?
Not confirmed. CVE-2026-13293 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. EPSS currently estimates a 0.56% probability of exploitation in the next 30 days.
How severe is CVE-2026-13293?
CVE-2026-13293 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-13293?
Yes. A fix has been recorded for CVE-2026-13293. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13293 affect?
CVE-2026-13293 affects IBM MQ 9.1.0.0 - 9.1.0.37 LTS, IBM MQ 9.2.0.0 - 9.2.0.43 LTS, IBM MQ 9.3.0.0 - 9.3.0.41 LTS / 9.3.0.0 - 9.3.5.1 CD, IBM MQ 9.4.0.0 - 9.4.0.25 LTS / 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-13293?
Apply IBM MQ updates immediately; restrict MQ access and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated remote attacker can execute arbitrary code on the MQ host via deserialization of untrusted data.
Immediate action required
- affected>= 9.1.0.0 and <= 9.1.0.37 LTS
- affected>= 9.2.0.0 and <= 9.2.0.43 LTS
- affected>= 9.3.0.0 and <= 9.3.0.41 LTS
- affected>= 9.3.0.0 and <= 9.3.5.1 CD
- affected>= 9.4.0.0 and <= 9.4.0.25 LTS
- affected>= 9.4.0.0 and <= 9.4.5.1 CD
- affected10.0.0.0
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.