IBM i 3.7 · Version Status

IBM i 3.7 End of Life Date

IBM i 3.7 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

⚠ IBM i 3.7 is past end of life. This version no longer receives security patches. 9962 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 30, 1999
9962 days past EOL
Latest Release
3.7
Standard release
Release Date
Nov 8, 1996
IBM i 3.7 series
Lifecycle detail

IBM i 3.7 was released on November 8, 1996 and support ended on June 30, 1999 — a supported lifespan of 2 years and 8 months, shorter than the 3 years and 11 months median for IBM i releases. The last patch it will ever receive is 3.7, published November 8, 1996 — 2 years and 8 months before support ended. It has been without security patches for 27 years and 4 months. 12 newer IBM i releases have shipped since.

← IBM i 3.2 All IBM i versions IBM i 4.1 →
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/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 →  ·  View score card →
Recommended upgrade path
IBM i 7.6
Latest release: 7.6.0 · EOL: Supported
View full IBM i timeline →
Extended Support
Extended IBM i 3.7 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All IBM i Versions
VersionLatestEOL DateStatus
2.1 2.1.1 Jun 30, 1994 EOL
2.2 2.2 Mar 31, 1995 EOL
2.3 2.3 May 31, 1996 EOL
3.0 3.0.5 May 31, 1997 EOL
3.1 3.1 Oct 31, 1998 EOL
3.2 3.2 May 31, 2000 EOL
3.6 3.6 Oct 31, 1998 EOL
→ 3.7 3.7 Jun 30, 1999 EOL

What does IBM i 3.7 end of life mean?

When IBM i 3.7 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running IBM i 3.7 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to IBM i 7.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does IBM i 3.7 reach end of life?
IBM i 3.7 reached end of life on June 30, 1999. This version is no longer receiving security patches.
Is IBM i 3.7 still supported?
No. IBM i 3.7 reached end of life on June 30, 1999 and is no longer receiving security patches.
What should I upgrade to from IBM i 3.7?
The recommended upgrade from IBM i 3.7 is IBM i 7.6 — the latest actively supported version. Check the IBM i full timeline for all supported versions.
What are the security risks of running IBM i 3.7 past EOL?
When IBM i 3.7 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL IBM i should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →