IBM z/OS · Lifecycle Status

IBM z/OS End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all IBM z/OS versions. Dates read at the vendor's own lifecycle pages (ibm.com). Updated at every deploy.

✓ IBM z/OS 3.2.0 is actively supported. No versions approaching EOL in the next 6 months.

IBM z/OS 3.2 is supported, with no end-of-life or end-of-support date announced yet. 5 of 7 tracked IBM z/OS versions are past end of life; the most recent to reach it, 2.5, did so on September 30, 2026. The full IBM z/OS lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
Latest Active
3.2.0
3.2 series
Next EOL
—
None upcoming
Active Versions
2
of 7 total
EOL Versions
5
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
CPE Identifier
cpe:2.3:o:ibm:z\/os
The Common Platform Enumeration name vulnerability scanners and CVE records use for IBM z/OS. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 20142015201620172018201920202021202220232024202520262.12.22.32.42.53.13.2TODAY
5 versions of IBM z/OS are past end of life — standard security patches have stopped; 2 of them are still covered by Extended support. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateExtended SupportDaysStatus
2.1 2.1.0 Sep 30, 2013 Sep 30, 2018 Jan 31, 2026
Extended support (ended)
2948 days past EOL EOL
2.2 2.2.0 Sep 30, 2015 Sep 30, 2020 Sep 30, 2027
Extended support
2217 days past EOL EOL
2.3 2.3.0 Sep 29, 2017 Sep 30, 2022 — 1487 days past EOL EOL
2.4 2.4.0 Sep 30, 2019 Sep 30, 2024 — 756 days past EOL EOL
2.5 2.5.0 Sep 30, 2021 Sep 30, 2026 Sep 30, 2029
Extended support
26 days past EOL EOL
3.1 3.1.0 Sep 29, 2023 TBD — Supported Active
3.2 3.2.0 Sep 30, 2025 TBD — Supported Active
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
EOL date vs extended support. The EOL Date column is the end of standard, included support. Extended support terms vary by vendor. Check whether the programme covers you before relying on these dates. 2 versions of IBM z/OS are past the standard EOL date but still inside the extended support window.
IBM z/OS EOL status badge Live EOL badge for your README — updates automatically at every build. [![IBM z/OS EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fzos.json)](https://endoflife.ai/zos)

IBM z/OS lifecycle status — the real story

z/OS is the operating system of the IBM mainframe — the machines still clearing a large share of the world's card payments, insurance claims, and bank ledgers — and its lifecycle runs with a regularity most vendors should envy: a release every two years (each September), five years of support minimum, then a three-year paid Service Extension. Under IBM's 'Enhanced' policy those dates are announced in formal letters, not blog posts.

The date that matters now: z/OS 2.5 reached end of support on September 30, 2026, and IBM's lifecycle entry for it (last updated 2026-09-30) prints "Completion of Extended, Sustained, Extension availability" as 2029-09-30, so paid extension runs to September 30, 2029. Its successors 3.1 (GA September 2023) and 3.2 (GA September 2025, alongside the z17 hardware) carry no announced end dates yet — the five-year minimum puts them no earlier than 2028 and 2030. Notably, 2.5's withdrawal from marketing already happened in January 2024: you cannot buy your way back onto it.

Mainframe estates rarely miss these dates by accident — they miss them because a z/OS upgrade drags an ecosystem (CICS, Db2, IMS, COBOL compilers, ISV tools) through recertification. That is why IBM's paid extensions exist and why third-party mainframe support is a thriving market: for shops mid-migration, the bridge is often not optional. Versions 2.1 and 2.2 illustrate the pattern — their paid extensions ran or run seven-plus years past general availability.

IBM z/OS release and support pattern

Across the 7 release lines with a published release date, IBM z/OS has shipped a new line roughly every 2 years (median interval). A line typically stays in standard support for about 5 years from its release to its standard-support end date (measured on the 5 lines with both dates published).

Of the 7 release lines tracked, 5 are past end of life and 2 are still within support. The newest line, 3.2, was released September 30, 2025. No end-of-life date is currently published for the 2 supported lines. Upstream also publishes an extended-support phase for 3 lines, shown in the table above.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does IBM z/OS end of life mean for your organization?

When a version of IBM z/OS reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL IBM z/OS should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when IBM z/OS reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your IBM z/OS version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get IBM z/OS Support Options

IBM z/OS has 5 versions past end of life — standard security patches have stopped; 2 of them are still covered by Extended support, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for IBM z/OS is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for IBM z/OS?
See the full table above for all IBM z/OS version EOL dates.
When is the IBM z/OS support end date?
Each IBM z/OS version has its own support end date — see the table above for every version's date.
What is the latest supported version of IBM z/OS?
The latest active version of IBM z/OS is 3.2.0. Always verify against the table above as support windows can change.
What happens when IBM z/OS reaches end of life?
When IBM z/OS reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of IBM z/OS?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL IBM z/OS versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.
Deep Dive
Version guide
IBM z/OS 2.5 End of Support: September 30, 2026 — the Three-Year Paid Extension, and the Move to 3.1 or 3.2
→

Related Products

✓ 15 of 15 lifecycle dates vendor-sourced · read from IBM (product lifecycle list) on 2026-10-20 · confidence: 14 high, 1 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (ibm.com) · Generated at build time · How we source data →
IBM z/OS end-of-life status badge