Complete end-of-life dates, support windows, and security status for all Sapmachine versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 10 | 10.0.2 | Mar 21, 2018 | Sep 25, 2018 | 2783 days past EOL | EOL |
| 11 LTS | 11.0.30 | Jan 16, 2019 | Dec 1, 2024 | 524 days past EOL | EOL |
| 12 | 12.0.2 | Mar 21, 2019 | Sep 18, 2019 | 2425 days past EOL | EOL |
| 13 | 13.0.2 | Sep 18, 2019 | Mar 18, 2020 | 2243 days past EOL | EOL |
| 14 | 14.0.2 | Mar 18, 2020 | Sep 16, 2020 | 2061 days past EOL | EOL |
| 15 | 15.0.2 | Sep 16, 2020 | Mar 15, 2021 | 1881 days past EOL | EOL |
| 16 | 16.0.2 | Mar 15, 2021 | Sep 14, 2021 | 1698 days past EOL | EOL |
| 17 LTS | 17.0.19 | Sep 14, 2021 | Sep 1, 2026 | 115 days remaining | Warning |
| 18 | 18.0.2.1 | Mar 21, 2022 | Sep 19, 2022 | 1328 days past EOL | EOL |
| 19 | 19.0.2 | Sep 19, 2022 | Mar 17, 2023 | 1149 days past EOL | EOL |
| 20 | 20.0.2 | Mar 17, 2023 | Sep 19, 2023 | 963 days past EOL | EOL |
| 21 LTS | 21.0.11 | Sep 18, 2023 | Sep 1, 2028 | 846 days remaining | Active |
| 22 | 22.0.2 | Mar 18, 2024 | Sep 17, 2024 | 599 days past EOL | EOL |
| 23 | 23.0.2 | Sep 18, 2024 | Mar 18, 2025 | 417 days past EOL | EOL |
| 24 | 24.0.2 | Mar 19, 2025 | Sep 16, 2025 | 235 days past EOL | EOL |
| 25 LTS | 25.0.3 | Sep 16, 2025 | Sep 30, 2030 | 1605 days remaining | Active |
| 26 | 26.0.1 | Mar 18, 2026 | Sep 15, 2026 | 129 days remaining | Warning |
When a Sapmachine 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 Sapmachine 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 →