Complete end-of-life dates, support windows, and security status for all Ibm Semeru Runtime versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 8 LTS | 8u482-b08 | Sep 16, 2021 | Dec 31, 2030 | 1697 days remaining | Active |
| 11 LTS | 11.0.30+7.1 | Sep 16, 2021 | Oct 31, 2027 | 540 days remaining | Active |
| 17 LTS | 17.0.18+8.1 | Dec 9, 2021 | Oct 31, 2027 | 540 days remaining | Active |
| 21 LTS | 21.0.10+7.1 | Sep 22, 2023 | Dec 31, 2029 | 1332 days remaining | Active |
| 22 | 22.0.2+9 | May 21, 2024 | Sep 18, 2024 | 598 days past EOL | EOL |
| 23 | 23.0.2+7 | Sep 18, 2024 | Mar 31, 2025 | 404 days past EOL | EOL |
| 24 | 24.0.2+12 | Mar 31, 2025 | Sep 25, 2025 | 226 days past EOL | EOL |
| 25 LTS | 25.0.2+10.1 | Sep 25, 2025 | Sep 30, 2030 | 1605 days remaining | Active |
| 26 | 26+35 | Mar 18, 2026 | Sep 30, 2026 | 144 days remaining | Warning |
When a Ibm Semeru Runtime version 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Ibm Semeru Runtime 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →