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.0.0 | Initial release (both Continuous Delivery and LTS) | 16 June 2026* | Not announced | 28 | 2 | 2 |
* The listed release date applies to IBM MQ on distributed platforms. The IBM MQ Appliance release date is 16th July 2026.
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.0.0 Initial release (both LTS and Continuous Delivery) for Windows, UNIX and IBM i
(Last modified: June 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 | ||
| 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. | ||
| 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 |
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"ARM Category":[{"code":"a8m0z0000001eskAAA","label":"Retired-\u003EAPARs \u0026 PTFs"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF012","label":"IBM i"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"10.0.0"}]
Was this topic helpful?
Document Information
Modified date:
16 June 2026
UID
ibm17276511