Vitess 17 · Version Status
Vitess 17 End of Life Date
Vitess 17 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Vitess 17 is past end of life. This version no longer receives security patches. 863 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 27, 2024
863 days past EOL
Latest Release
17.0.7
Standard release
Release Date
Jun 27, 2023
Vitess 17 series
Where these dates come from
End of lifeJun 27, 2024endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseJun 27, 2023endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Vitess 17 was released on June 27, 2023 and support ended on June 27, 2024 — a supported lifespan of 1 year, in line with the 1 year median for Vitess releases. Its latest release on record is 17.0.7, published May 8, 2024 — 2 months before support ended. It has been past its end-of-life date for 2 years and 4 months. 4 newer Vitess releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Vitess 17 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Vitess 17 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version 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?
What are the security risks of running Vitess 17 past EOL?
Since Vitess 17 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Vitess should migrate immediately or implement compensating controls.