IBM MQ is widely used enterprise messaging middleware; a heap overflow enabling DoS or privilege escalation is high-impact and should reach all IT/security teams.
CVE-2026-10575
Heap overflow in IBM MQ MQPUT headers allows DoS or possible privilege escalation.
Is CVE-2026-10575 being exploited?
Not confirmed. CVE-2026-10575 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-10575?
CVE-2026-10575 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-10575?
Yes. A fix has been recorded for CVE-2026-10575. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-10575 affect?
CVE-2026-10575 affects IBM MQ. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-10575?
Apply IBM's MQ security update immediately; restrict MQ access and monitor MQPUT traffic.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can craft malformed MQPUT distribution headers to trigger heap overflow, causing DoS or potential privilege escalation on IBM MQ servers.
Patch when possible
- 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.