Vitess 17
Vitess 17
The Vitess 17 reached end of service life on Jun 27, 2024 — Vitess no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Vitess 17 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- vitess
- release
- 17
- product Label
- Vitess
- release Label
- 17
- codename
- lts
- latest Version
- 17.0.7
- release Date
- 2023-06-27
- maintained
- source Url
- https://endoflife.date/vitess
Lifecycle Dates
- End of Service Life
- Jun 27, 2024
- Last OEM Support
- Jun 27, 2024
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Vitess 17 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Vitess 17?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Vitess 17 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Vitess 17 Support: Frequently Asked Questions
Is the Vitess 17 still supported?
Vitess ended support for the Vitess 17 on Jun 27, 2024 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Vitess 17 end of service life (EOSL) date?
Vitess lists the end of service life for the Vitess 17 as Jun 27, 2024.
Can I keep using the Vitess 17 after its EOSL date?
Yes. EOSL means Vitess stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Vitess 17 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Vitess 17
2 published CVEs affect the Vitess 17, including 2 rated critical or high severity. Vitess no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2026-27969 | CRITICAL | 9.3 | Feb 26, 2026 | Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g. an S3 bucket) can manipulate backup manifest files so that files in the manifest — which may be files that they have also added to the manifest and backup contents — are written to any accessible location on restore. This is a common path traversal security issue. This can be used to provide that attacker with unintended/u |
| CVE-2026-27965 | HIGH | 8.4 | Feb 26, 2026 | Vitess is a database clustering system for horizontal scaling of MySQL. Prior to versions 23.0.3 and 22.0.4, anyone with read/write access to the backup storage location (e.g. an S3 bucket) can manipulate backup manifest files so that arbitrary code is later executed when that backup is restored. This can be used to provide that attacker with unintended/unauthorized access to the production deployment environment — allowing them to access information available in that environment as well as run |