IBM MQ 9.2 LTS End-of-Life: Action Plan (September 30, 2025)

The Clock is Ticking on IBM MQ 9.2 LTS

IBM MQ 9.2 LTS reaches end of life on September 30, 2025 — roughly three months from now. After that date, IBM will no longer provide patches, bug fixes, or security updates. Vendor SLAs for this version will cease entirely.

If your organization still runs IBM MQ 9.2, a full migration to a newer release before the deadline is no longer realistic for most estates. The goal now is to manage the risk until you can complete a migration. This article provides a direct, week-by-week action plan to protect your environment, document exposure for auditors and insurers, and secure a support safety net for day one after EOL.

What Changes on September 30, 2025?

• No more security patches or fixes — zero-day vulnerabilities will remain unpatched for IBM MQ 9.2.
• No vendor support — IBM will not respond to tickets or SLAs for this version.
• Regulatory exposure — compliance frameworks (PCI DSS, SOX, etc.) often require supported software. Auditors will flag an unsupported version.
• Insurance implications — cyber insurance policies may exclude coverage for known vulnerabilities in unsupported software.

Week-by-Week Action Checklist

Every week counts. Use this timeline to stay on track.

Week 1: Complete Inventory

• Identify every server, container, and environment running IBM MQ 9.2 LTS.
• Document the application dependencies, queue managers, and integration points.
• Note any third-party integrations (e.g., SAP, Salesforce, custom apps) that rely on this version.

Week 2: Risk Assessment & Isolation

• For each instance, determine if it can be isolated: restrict network access, disable unnecessary listeners, and tighten firewall rules.
• Apply all available fixes from IBM before EOL. This is your last chance to get vendor-issued patches.
• Document compensating controls (e.g., IPS signatures, additional logging) for environments that cannot be migrated.

Week 3: Document Exposure

• Create a formal risk register for your audit and compliance teams. Include:
  • The version, EOL date, and number of affected systems.
  • Planned migration timeline (even if it’s six months out).
  • Compensating controls in place.
• Share this document with your internal audit, legal, and insurance representatives.
• Update your business continuity plan to explicitly note the unsupported version.

Week 4: Secure a Support Safety Net

• Evaluate third-party maintenance for IBM MQ 9.2. A reputable provider can continue delivering critical patches and emergency bug fixes after September 30, keeping your environment supported and compliant.
• Contact a provider to initiate onboarding. Ensure contracts are in place before the EOL date.

Week 5+: Harden and Monitor

• Increase monitoring and alerting for IBM MQ 9.2 systems. Consider adding a SIEM or dedicated log analysis.
• Run vulnerability scans weekly until the migration is complete.
• Begin planning a phased migration to a newer version (e.g., IBM MQ 9.3 or 9.4). The extra time from third-party support gives you a safe window to test and roll out.

Why Third-Party Support Makes Sense Now

When the vendor stops supporting a product, you’re not alone. Third-party support providers can extend the safe, supported life of IBM MQ 9.2 LTS well past the official end of life. They deliver:

• Security patches and hotfixes for critical vulnerabilities.
• Technical support with SLAs that match or exceed vendor terms.
• Compliance coverage — auditors accept third-party support as a valid mitigation.

For many IT teams, the few months between now and September 30 are best spent on inventory, hardening, and documentation, while letting a third-party partner handle the support gap. This approach reduces panic and gives you a realistic timeline for a full migration.

Next Steps

1. Complete the inventory by the end of this week.
2. Apply all last vendor patches before September 30.
3. Document your risk posture for auditors and insurers.
4. Secure a third-party support contract for day one after EOL.

If you need to discuss options for keeping IBM MQ 9.2 supported after the cutoff, contact our team. We can help you assess your environment and provide a tailored support plan.

---

For more information about IBM lifecycle management, see our IBM software page.