Fix Readme
Abstract
IBM MQ provides regular updates that include new features and defect fixes. This document contains lists of available fixes for the IBM MQ 10.0 initial release and subsequent Continuous Delivery (CD) releases and CD Cumulative Security Updates (CSUs).
Content
This document lists the available fixes for the initial IBM MQ 10.0 LTS release, along with subsequent Continuous Delivery (CD) releases and CD Cumulative Security Updates (CSUs). For more information on the types of release, refer to the IBM MQ release types and versioning section of the product documentation.
| List of fixes | Release type | Release date | End of defect support | Total fixes | Security fixes | HIPER fixes |
| IBM MQ 10.0.1.0 | Continuous Delivery release | 13 October 2026 | 13 October 2027 | 53 | 33 | 3 |
| IBM MQ 10.0.0.5 | First maintenance release (both Continuous Delivery and LTS)1 | 10 September 2026 | Not announced | 50 | 32 | 0 |
| IBM MQ 10.0.0.0 | Initial release (both Continuous Delivery and LTS) | MQ Dist: 16 June 2026 / MQ Appliance: 16 July 2026 | Not announced | 31 | 2 | 2 |
Note 1: The IBM MQ 10.0.0.5 initial maintenance release applies to all users, whether they follow the MQ Long Term Support (LTS) release stream or the Continuous Delivery (CD) release stream. Users who follow the LTS stream should apply cumulative security update 10.0.0.6, and then later 10.0.0.x maintenance releases as they become available. Users who follow the CD stream should upgrade to 10.0.1.0, and then later 10.0.x.x releases as they become available. For the MQ 10 LTS fixes, see Fix list for IBM MQ 10.0 LTS.
Download the latest IBM MQ fixes from the IBM MQ Recommended Fixes and Planned Maintenance release dates page.
Security bulletins and vulnerability risk information can be found at IBM Product Security Central.
Example table
| Security | HIPER | APAR / known issue | Description |
| ✓ | AB12345 | CVE-XXXX-XXXXX (security/integrity exposure) [CVSS base score 5.3] | |
| ✓ | ZY98765 | Description of a HIPER |
IBM MQ 10.0.1.0 Continuous Delivery Release for Windows and UNIX
(Last modified: Oct 2026)
| Is Security | Is HIPER | known issue | Description |
| ✓ | DT472391 | IBM MQ CVE-2026-10572, IBM MQ Appliance CVE-2026-10572 [CVSS base score 8.8] | |
| ✓ | DT472392 | IBM MQ CVE-2026-10574, IBM MQ Appliance CVE-2026-10574 [CVSS base score 8.8] | |
| ✓ | DT472702 | IBM MQ CVE-2026-10743, IBM MQ Appliance CVE-2026-10743 [CVSS base score 8.8] | |
| ✓ | DT472703 | IBM MQ CVE-2026-10859 [CVSS base score 7.5] | |
| ✓ | DT473111 | IBM MQ CVE-2026-14252 [CVSS base score 6.2] | |
| ✓ | DT473347 | IBM MQ CVE-2026-11724 [CVSS base score 8.5] | |
| ✓ | DT473422 | IBM MQ CVE-2026-11376, IBM MQ Appliance CVE-2026-11376 [CVSS base score 8.8] | |
| ✓ | DT473621 | IBM MQ CVE-2026-12148 [CVSS base score 7.5] | |
| ✓ | DT473747 | IBM MQ CVE-2026-12356 [CVSS base score 7.5] | |
| ✓ | DT474363 | IBM MQ CVE-2026-12660 [CVSS base score 2.7] | |
| ✓ | DT474627 | IBM MQ CVE-2026-13271 [CVSS base score 8.1] | |
| ✓ | DT474692 | IBM MQ CVE-2026-13292 [CVSS base score 8.8] | |
| ✓ | DT474698 | IBM MQ CVE-2026-13284 [CVSS base score 7.1] | |
| ✓ | DT474700 | IBM MQ CVE-2026-13289 [CVSS base score 7.1] | |
| ✓ | DT474965 | IBM MQ CVE-2026-12665, IBM MQ Appliance CVE-2026-12665 [CVSS base score 8.1] | |
| ✓ | DT495431 | IBM MQ CVE-2026-12350 [CVSS base score 6.5] | |
| ✓ | DT495438 | IBM MQ CVE-2026-12155, IBM MQ Appliance CVE-2026-12155 [CVSS base score 6.5] | |
| ✓ | DT495443 | IBM MQ CVE-2026-11829, IBM MQ Appliance CVE-2026-11829 [CVSS base score 6.5] | |
| ✓ | DT498516 | IBM MQ CVE-2026-10842, CVE-2026-11897, CVE-2026-15057, Multiple CVEs, CVE-2026-16192, CVE-2026-10571 and CVE-2026-49875 and IBM MQ Appliance Multiple CVEs [CVSS base score 9.8] | |
| ✓ | DT498676 | IBM MQ Multiple CVEs, IBM MQ Multiple CVEs, [CVSS base score 9.1] | |
| ✓ | DT498936 | Description not yet available(security/integrity exposure) [CVSS base score 9.6] | |
| ✓ | DT500337 | IBM MQ Appliance Multiple CVEs [CVSS base score 8.8] | |
| ✓ | DT500561 | IBM MQ CVE-2026-18142, IBM MQ Appliance CVE-2026-18142 [CVSS base score 7.1] | |
| ✓ | DT500572 | IBM MQ CVE-2026-11828 [CVSS base score 5.9] | |
| ✓ | DT500575 | IBM MQ CVE-2026-11831, IBM MQ Appliance CVE-2026-11831 [CVSS base score 5.4] | |
| ✓ | DT500582 | IBM MQ CVE-2026-12343, IBM MQ Appliance CVE-2026-12343 [CVSS base score 6.5] | |
| ✓ | DT500588 | IBM MQ CVE-2026-12727, IBM MQ Appliance CVE-2026-12727 [CVSS base score 4.3] | |
| ✓ | ✓ | DT500592 | IBM MQ CVE-2026-12670, IBM MQ Appliance CVE-2026-12670 [CVSS base score 5.3] |
| ✓ | DT500593 | IBM MQ CVE-2026-12669, IBM MQ Appliance CVE-2026-12669 [CVSS base score 3.1] | |
| ✓ | DT500603 | IBM MQ CVE-2026-12550, IBM MQ Appliance CVE-2026-12550 [CVSS base score 5.4] | |
| ✓ | DT500605 | Description not yet available(security/integrity exposure) [CVSS base score 5.4] | |
| ✓ | DT502223 | Description not yet available(security/integrity exposure) [CVSS base score 7.5] | |
| ✓ | DT502463 | IBM MQ CVE-2026-78254 [CVSS base score 7.4] | |
| ✓ | DT457002 | The IBM MQ dmpmqmsg program can corrupt a message when dumping its contents in text line output format with 'dmpmqmsg -d t' | |
| ✓ | DT466594 | The dmpmqcfg command does not back up the IBM MQ object attribute 'DESCR' properly. | |
| DT378265 | SIGSEGV while processing in publish/subscribe using wildcard topic strings. Queue manager may end immediately. | ||
| DT428237 | Improve diagnostic outputs in the FFST with Probe Id IN330050 caused by corrupted installation of IBM MQ | ||
| DT429767 | An IBM MQ process became unresponsive when trace was turned on or off. | ||
| DT443436 | IBM MQ's mqperfck command did not support cluster sender channels, reporting an error when a cluster sender channel name was supplied. | ||
| DT449192 | IBM MQ reports a warning related to the nfs-utils package during Pacemaker uninstallation. | ||
| DT452115 | Prevent the IBM MQ queue and topic attribute CUSTOM('CAPEXPRY(0)') from expiring messages immediately | ||
| DT457618 | IBM MQ mqconfig command reports "user name does not exist" and "basename: missing operand" errors in container. | ||
| DT459810 | Outbound MQIPT TLS connection fails with a "the trustAnchors parameter must be non-empty" exception. | ||
| DT461571 | The IBM MQ resource adapter (RA) and IBM MQ RA for Jakarta Messaging incorrectly allow multiple sessions to be created from a single connection. | ||
| DT462237 | IBM MQ Appliance may report excessive error log entries containing `unexpected eof while reading ` | ||
| DT463237 | IBM MQ RDQM resource agents could fail to start if IBM MQ libraries were unavailable when invoked by Pacemaker. | ||
| DT470814 | IBM MQ DISPLAY CHANNEL command may fail intermittently with AMQ8101E. | ||
| DT472893 | Unable to log into the MQ Console after applying a Fix Pack or Cumulative Security Update (CSU) | ||
| DT474076 | IBM MQ Resource Adapter - "java.io.NotSerializableException" occurring from the "XARWrapper" class. | ||
| DT474483 | IBM MQ 9.3.x: Queue Manager enters CrashLoopBackOff state due to log record corruption, generating FDCs with probes AQ16500, AO028002, ZX000040 | ||
| DT498935 | JMSAdmin fails to retrieve JMS administered objects from an LDAP server, reporting "Object is not an IBM MQ classes for JMS administered object". | ||
| DT499566 | LUKS resource monitor operation times out due to a CPU spike causing Queue manager restarts on an appliance | ||
| DT500157 | When an IBM MQ Java client application executed with trace enabled, the contents of data buffers were not dumped. Instead, only the Java object ID was reported. |
IBM MQ 10.0.0.0 Initial release (both LTS and Continuous Delivery) for Windows, UNIX and IBM i
(Last modified: July 2026)
| Is Security | Is HIPER | known issue | Description |
| ✓ | DT469462 | Description not yet available(security/integrity exposure) [CVSS base score 7.5] | |
| ✓ | DT470961 | Description not yet available(security/integrity exposure) [CVSS base score 7.5] | |
| ✓ | DT459574 | MQ Managed File Transfer (MFT) agent generates an FDC or ABEND file with a cause of "BFGEV0004E: An internal error has occurred". | |
| ✓ | DT463019 | AMQ9456I: "Update not received for object" for remote cluster queues | |
| DT428275 | Messages returned as "Modified" by AMQP clients are not handled correctly by the IBM MQ AMQP service | ||
| DT429847 | Local queue manager writes a Failure Data Capture (FDC) record with Probe Id KN150010, and does not merge properties added by a Before-MQPUT exit correctly with those arriving over a channel from a remote queue manager | ||
| DT433371 | FDC with probe ID AT081010 generated unnecessarily, causing unwanted consumption of disk space | ||
| DT443033 | Documentation for IBM MQ Appliance does not reflect the correct UDP ports used for HA heartbeat communication in version 9.3.x and later. | ||
| DT450035 | Protocol error FDC (ProbeID CO547103) generated by a queue manager when a MQ-JMS application is connected | ||
| DT452000 | Misleading error comment in FDC generated during AutoConfig stanza processing in Japanese locale. | ||
| DT453449 | Application hostname/IP address not specified in a FDC when a protocol error is reported | ||
| DT456115 | IBM MQ Application Activity Trace generates duplicate event messages when transmitting bulk messages under syncpoint. | ||
| DT456362 | IBM MQ 9.4 Appliance keyrestore command reports AMQ5530E when using LDAP | ||
| DT456825 | Performing concurrent IBM MQ Console or REST API operating system authentication requests can result in FDCs being generated. | ||
| DT457367 | Stopping a singular IBM MQ Resource Adapter (RA) deployment destroys all MQ connections across every RA deployment. | ||
| DT457794 | IBM MQ IPT requests a TLS certificate from client side even if 'SSLServerAskClientAuth=false' | ||
| DT458518 | IBM MQ MFT process controller erroneously maintains the "mqmftpc.pid" file. | ||
| DT458547 | IBM MQ AMQP Service fails to respond to drain requests in a timely manner. | ||
| DT458857 | AMQ9645E certificate label error when using SNI for per-channel certificate selection with PKCS#11 cryptographic stores | ||
| DT458890 | The amqrmppa process may terminate and generate an FFST with Probe ID XC130003 due to a memory exception in ccxGiveConv | ||
| DT458973 | Add diagnostic controls for the use of the SYSTEM.ADMIN.COMMAND.QUEUE | ||
| DT459211 | WRKMQMQ with an invalid queue name such as SYSTEM&* can leave the job connected to a Queue Manager. As a result, a later WRKMQM can show other active Queue Managers as INACTIVE. | ||
| DT460458 | Unexpected behaviour when the MQ classes for JMS and classes for Jakarta Messaging perform backout processing on messages with a COA report option set. | ||
| DT461314 | MQ application MQOPEN or MQPUT for an MQ cluster queue returns with MQRC_PUT_INHIBITED but one or more remote instances are not put-disabled | ||
| DT461401 | After using the IBM MQ cluster commands WRKMQMCL or WRKMQMCLQ, Queue Manager status shown by WRKMQM can be incorrect. Active Queue Managers can be displayed as INACTIVE after one of these cluster commands is run on IBM i. | ||
| DT462909 | MQ client library code in application restores SIGPIPE handler incompletely after last MQDISC | ||
| DT463391 | The '-n' parameter was not recognised when running the mqperfck command on windows | ||
| DT464491 | IBM MQ Native HA CRR rebase fails when the recovery set is greater than 4GB | ||
| DT464685 | IBM MQ Native HA may generate one or more First Failure Data Capture (FDC) files containing relevant diagnostic information. | ||
| DT466394 | Corrections needed for some AMQP error message codes | ||
| DT468272 | IBM MQ Appliance queue manager configuration file getting corrupted after the filesystem reached 100% utilisation. |
Was this topic helpful?
Document Information
Modified date:
03 November 2026
UID
ibm17276511