Tarantool 3.2 · Version Status
Tarantool 3.2 End of Life Date
Tarantool 3.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
Tarantool 3.2 reaches end of life on August 26, 2026. Plan your migration now — 109 days remaining.
EOL Date
Aug 26, 2026
109 days remaining
Latest Release
3.2.3
Standard release
Release Date
Aug 26, 2024
Tarantool 3.2 series
| Version | Latest | EOL Date | Status |
|---|
| 1.10 LTS |
1.10.15 |
May 24, 2023 |
EOL |
| 2.2 |
2.2.3 |
Apr 20, 2020 |
EOL |
| 2.3 |
2.3.3 |
Jul 17, 2020 |
EOL |
| 2.4 |
2.4.3 |
Oct 22, 2020 |
EOL |
| 2.5 |
2.5.3 |
Dec 30, 2020 |
EOL |
| 2.6 |
2.6.3 |
Apr 21, 2021 |
EOL |
| 2.7 |
2.7.3 |
Aug 19, 2021 |
EOL |
| 2.8 |
2.8.4 |
Apr 25, 2022 |
EOL |
What does Tarantool 3.2 end of life mean?
When Tarantool 3.2 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Tarantool 3.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Tarantool 3.7 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Tarantool 3.2 reach end of life?
Tarantool 3.2 reached end of life on August 26, 2026. That is 109 days remaining.
Is Tarantool 3.2 still supported?
Tarantool 3.2 is still supported but approaching end of life on August 26, 2026. Begin planning your migration now.
What should I upgrade to from Tarantool 3.2?
The recommended upgrade from Tarantool 3.2 is
Tarantool 3.7 — the latest actively supported version. Check the
Tarantool full timeline for all supported versions.
What are the security risks of running Tarantool 3.2 past EOL?
When Tarantool 3.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Tarantool should migrate immediately or implement compensating controls.