Vitess 17 · Version Status
Vitess 17 End of Life Date
Vitess 17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Vitess 17 is past end of life. This version no longer receives security patches. 681 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 27, 2024
681 days past EOL
Latest Release
17.0.7
Standard release
Release Date
Jun 27, 2023
Vitess 17 series
| Version | Latest | EOL Date | Status |
|---|
| 13 |
13.0.3 |
Feb 22, 2023 |
EOL |
| 14 |
14.0.5 |
Jun 28, 2023 |
EOL |
| 15 |
15.0.5 |
Oct 25, 2023 |
EOL |
| 16 |
16.0.7 |
Feb 28, 2024 |
EOL |
| → 17 |
17.0.7 |
Jun 27, 2024 |
EOL |
| 18 |
18.0.8 |
Nov 7, 2024 |
EOL |
| 19 |
19.0.10 |
Mar 6, 2025 |
EOL |
| 20 |
20.0.8 |
Jun 27, 2025 |
EOL |
What does Vitess 17 end of life mean?
When Vitess 17 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 Vitess 17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Vitess 24 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Vitess 17 reach end of life?
Vitess 17 reached end of life on June 27, 2024. This version is no longer receiving security patches.
Is Vitess 17 still supported?
No. Vitess 17 reached end of life on June 27, 2024 and is no longer receiving security patches.
What should I upgrade to from Vitess 17?
The recommended upgrade from Vitess 17 is
Vitess 24 — the latest actively supported version. Check the
Vitess full timeline for all supported versions.
What are the security risks of running Vitess 17 past EOL?
When Vitess 17 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 Vitess should migrate immediately or implement compensating controls.