Vitess 24
Vitess 24
The Vitess 24 reaches end of service life on Apr 30, 2027. 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 24 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
- 24
- product Label
- Vitess
- release Label
- 24
- codename
- lts
- latest Version
- 24.0.5
- release Date
- 2026-04-30
- maintained
- true
- source Url
- https://endoflife.date/vitess
Lifecycle Dates
- End of Service Life
- Apr 30, 2027
- Last OEM Support
- Apr 30, 2027
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Vitess 24 — 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 24?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Vitess 24 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 24 Support: Frequently Asked Questions
Is the Vitess 24 still supported?
Yes, but Vitess support for the Vitess 24 ends on Apr 30, 2027. 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 24 end of service life (EOSL) date?
Vitess lists the end of service life for the Vitess 24 as Apr 30, 2027.
Can I keep using the Vitess 24 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 24 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location. You get an indicative price within 24 hours and a firm quote within 48.
Known Vulnerabilities Affecting Vitess 24
2 published CVEs affect the Vitess 24, including 1 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-104252 | CRITICAL | 9.8 | Oct 13, 2026 | Vitess is a database clustering system for horizontal scaling of MySQL. Prior to 23.0.5 and 24.0.2, twopczHandler in go/vt/vttablet/tabletserver/twopcz.go writes the Action and dtid form values from the vttablet and vtcombo /twopcz HTTP debug endpoint into a text/html response without HTML escaping. Under the default allow-all ACL policy, a remote unauthenticated attacker can send an operator a crafted request that executes script in the operator's browser after the request is opened. The script |
| CVE-2026-65959 | MEDIUM | 5.3 | Aug 18, 2026 | Vitess is a database clustering system for horizontal scaling of MySQL. In 24.0.2 and earlier, the /debug/vrlog endpoint registered by addHttpEndpoint() in go/vt/vttablet/tabletmanager/vreplication/vrlog.go invokes vrlogStatsHandler() without acl.CheckAccessHTTP(r, acl.DEBUGGING), unlike comparable debug endpoints. A remote caller who can reach the vttablet debug HTTP port can bypass the configured security policy and stream VrLogStats data produced from NewVrLogStats().Send(), including literal |