IBM MQ Lifecycle policy

Product overview

IBM MQ is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Main capabilities

Networked or application service delivery
Administrative and operational interfaces
Versioned maintenance and security updates

Typical use

Used to provide application, infrastructure or operational services to other systems and users.

Deployment

Deployed on servers, virtual machines, containers or managed infrastructure.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	IBM MQ
Release	Lifecycle policy
Start or release	Not extracted
Lifecycle boundary	Continuous or not dated in the source
Date precision	Unknown

Known exploited vulnerabilities

Catalogue updated 29 Sep 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYEmpty

IBM MQ official lifecycle source

IBM MQ Operator and queue manager fixes are provided on the latest available CD release of the queue manager and IBM MQ Operator. IBM MQ Operator fixes are delivered through the Operator channel as a fix version, as part of ongoing scheduled release updates. | Deprecations and Removals | Q. How are deprecations and removals handled for the IBM MQ Operator? | Any value of .spec.version that is not the latest fix version might be marked as deprecated. Values of .spec.version are removed only in major changes in semantic version of the Operator (for example, when moving from IBM MQ Operator 1.x.y to 2.0.0). Values of .spec.version are not removed for at least six months from the initial CD release (as measured from the original CD release, not the most recent fix). | IBM MQ General | IBM MQ Appliance | IBM MQ Operator & Containers | Top of page | IBM MQ Support Lifecycle FAQ IBM MQ follows a continuous delivery model with regular update packages. Each update incrementally delivers new capability and defect fixes. Long Term Support (LTS) packages receive only security and defect fixes through fix packs and individual fixes, with no incremental functional enhancements. Feature IBM MQ Software IBM MQ Appliance IBM MQ Operator & Containers Support Policy Support Cycle-5 (Multiplatforms) Continuous Delivery (z/OS) Support Cycle-3 Support Cycle-2.5 LTS support duration 5 years minimum 3 years (no extension) 2.5 years Extended Support available? Yes, up to 4 additional years (defect fixes in year 1 only) No For Cloud Pak for Integration only, up to 4 additional years (defect fixes in year 1 only) 1 CD fix eligibility 12 months from GA or 2 most recent CD releases, whichever is longer Latest CD release; previous CD considered if less than 6 months old Latest CD release Are interim fixes provided on back-level fix packs? Yes (iFix/APAR on installed LTS level where possible) No, you must be on the latest fix pack of your chosen LTS No, you must be on the latest fix pack and revision Maintenance cadence Every 2 months - CD : Alternating CD and CSU releases - LTS : CSUs, of which 2-3 per year become fix packs, which include functional fixes Every 2 months - CD : Alternating CD and CSU releases - LTS : CSUs, of which 2-3 per year become fix packs, which include functional fixes Monthly CSU and fix pack updates through the Operator channel Roll-back supported? No, except for IBM MQ for z/OS backward migration for LTS releases No No 1 Extended support is available only for IBM MQ in containers, when you use certain versions of IBM Cloud Pak for Integration, identified in the tables on page Lifecycle dates for IBM MQ in containers . ⓘ Note for versions 9.0–9.3 only (previous support policy): Versions 9.0 through 9.3 of IBM MQ for Multiplatforms, IBM MQ for z/OS, and IBM MQ Appliance followed the Continuous Delivery policy. Long Term Support for IBM MQ for Multiplatforms and IBM MQ for z/OS was a minimum of 5 years with an option for up to 3 years of extended support. Long Term Support for IBM MQ Appliance was 3 years with no support extensions. These terms do not apply to current releases. System Requirements and Lifecycle links For supported operating systems and other system requirements on both CD and LTS releases, see the IBM MQ system requirements page . For available LTS and CD releases and latest fixes, see the IBM MQ planned maintenance and recommended fixes page . For available IBM MQ Operator and Container lifecycle information see Lifecycle dates for IBM MQ in containers . Continuous Delivery (CD) update packages You can request defect fixes for a CD update, according to the previous table. A CD update might be declared an LTS release, then be supported for a longer period according to the previous table. If a CD update is no longer eligible for defect fixes, update to a newer, eligible package; if the defect can be recreated, a fix will be provided. Fix Packs and Cumulative Security Updates (CSU) IBM MQ delivers two types of maintena

Official vendor lifecycle or product-change property. Extracted records require human review.

First collected 12 Sep 2026 · Last collected 21 Sep 2026 · Review state accepted

Open official vendor source