IBM Semeru Runtime 22 · Version Status

IBM Semeru Runtime 22 End of Life Date

IBM Semeru Runtime 22 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 Semeru Runtime 22 is past end of life. This version no longer receives security patches. 735 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 18, 2024
735 days past EOL
Latest Release
22.0.2+9
Standard release
Release Date
May 21, 2024
IBM Semeru Runtime 22 series
Lifecycle detail

IBM Semeru Runtime 22 was released on May 21, 2024 and support ended on September 18, 2024 — a supported lifespan of 4 months, shorter than the 5 years and 11 months median for IBM Semeru Runtime releases. It was not an LTS release; IBM Semeru Runtime reserves longer patch windows for its LTS versions. The last patch it will ever receive is 22.0.2+9, published September 10, 2024 — 8 days before support ended. It has been without security patches for 2 years. 4 newer IBM Semeru Runtime releases have shipped since.

← IBM Semeru Runtime 21 All IBM Semeru Runtime versions IBM Semeru Runtime 23 →
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 Semeru Runtime 27
Latest release: 27.0.0.0 · EOL: Mar 31, 2027
View full IBM Semeru Runtime timeline →
Extended Support
Extended IBM Semeru Runtime 22 support is available

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

Compare Options →
All IBM Semeru Runtime Versions
VersionLatestEOL DateStatus
8 LTS 8.0.504.0 Dec 31, 2030 Active
11 LTS 11.0.32.10 Oct 31, 2027 Active
17 LTS 17.0.20.10 Oct 31, 2027 Active
21 LTS 21.0.10+7.1 Dec 31, 2029 Active
22 22.0.2+9 Sep 18, 2024 EOL
23 23.0.2+7 Mar 31, 2025 EOL
24 24.0.2+12 Sep 25, 2025 EOL
25 LTS 25.0.4.10 Sep 30, 2031 Active

What does IBM Semeru Runtime 22 end of life mean?

When IBM Semeru Runtime 22 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 Semeru Runtime 22 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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

Frequently Asked Questions
When does IBM Semeru Runtime 22 reach end of life?
IBM Semeru Runtime 22 reached end of life on September 18, 2024. This version is no longer receiving security patches.
Is IBM Semeru Runtime 22 still supported?
No. IBM Semeru Runtime 22 reached end of life on September 18, 2024 and is no longer receiving security patches.
What should I upgrade to from IBM Semeru Runtime 22?
The recommended upgrade from IBM Semeru Runtime 22 is IBM Semeru Runtime 27 — the latest actively supported version. Check the IBM Semeru Runtime full timeline for all supported versions.
What are the security risks of running IBM Semeru Runtime 22 past EOL?
When IBM Semeru Runtime 22 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 Semeru Runtime should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →