Complete end-of-life dates, support windows, and security status for all Tarantool versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.10 LTS | 1.10.15 | Mar 7, 2018 | May 24, 2023 | 1081 days past EOL | EOL |
| 2.2 | 2.2.3 | Mar 22, 2019 | Apr 20, 2020 | 2210 days past EOL | EOL |
| 2.3 | 2.3.3 | Aug 2, 2019 | Jul 17, 2020 | 2122 days past EOL | EOL |
| 2.4 | 2.4.3 | Jan 10, 2020 | Oct 22, 2020 | 2025 days past EOL | EOL |
| 2.5 | 2.5.3 | Apr 20, 2020 | Dec 30, 2020 | 1956 days past EOL | EOL |
| 2.6 | 2.6.3 | Jul 17, 2020 | Apr 21, 2021 | 1844 days past EOL | EOL |
| 2.7 | 2.7.3 | Oct 23, 2020 | Aug 19, 2021 | 1724 days past EOL | EOL |
| 2.8 | 2.8.4 | Dec 30, 2020 | Apr 25, 2022 | 1475 days past EOL | EOL |
| 2.10 | 2.10.8 | May 22, 2022 | May 24, 2023 | 1081 days past EOL | EOL |
| 2.11 LTS | 2.11.9 | May 24, 2023 | May 24, 2027 | 380 days remaining | Active |
| 3.0 | 3.0.2 | Dec 26, 2023 | Apr 16, 2024 | 753 days past EOL | EOL |
| 3.1 | 3.1.2 | Apr 16, 2024 | Aug 26, 2024 | 621 days past EOL | EOL |
| 3.2 | 3.2.3 | Aug 26, 2024 | Aug 26, 2026 | 109 days remaining | Warning |
| 3.3 | 3.3.4 | Nov 29, 2024 | Nov 29, 2026 | 204 days remaining | Active |
| 3.4 | 3.4.2 | Apr 15, 2025 | Apr 14, 2027 | 340 days remaining | Active |
| 3.5 | 3.5.1 | Aug 27, 2025 | Already EOL | Supported | Active |
| 3.6 | 3.6.2 | Dec 12, 2025 | Already EOL | Supported | Active |
| 3.7 | 3.7.0 | Apr 22, 2026 | Already EOL | Supported | Active |
When a Tarantool 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 Tarantool 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 →