Vitess 23
Vitess 23
The Vitess 23 reaches end of service life on Nov 4, 2026. Third-party support keeps it managed past that date — issue management, vulnerability remediation, and compliance maintenance from 24/7 engineers.
24/7 engineers own your Vitess 23 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
- 23
- product Label
- Vitess
- release Label
- 23
- codename
- lts
- latest Version
- 23.0.5
- release Date
- 2025-11-04
- maintained
- true
- source Url
- https://endoflife.date/vitess
Lifecycle Dates
- End of Service Life
- Nov 4, 2026
- Last OEM Support
- Nov 4, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Vitess 23 — 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 23?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Vitess 23 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 23 Support: Frequently Asked Questions
Is the Vitess 23 still supported?
Yes, but Vitess support for the Vitess 23 ends on Nov 4, 2026. You can upgrade on the vendor's schedule, or move to third-party support and keep the release you're on — issues managed, vulnerabilities remediated, compliance maintained.
When is the Vitess 23 end of service life (EOSL) date?
Vitess lists the end of service life for the Vitess 23 as Nov 4, 2026.
Can I keep using the Vitess 23 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 23 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 23
2 published CVEs affect the Vitess 23, including 2 rated critical or high severity. Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.
| 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 |