Synced 02 Nov 2026 13:39 UTC Account
← Vitess

Vitess vulnerabilities: known CVEs & security history

CNCF · Database · 6 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Vitess release lines — 6 in total. A CVE here doesn't mean your version is affected — check Vitess's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
2
critical severity
0
ransomware-linked

Known Vitess CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-27965 critical 9.9 0% 2026
CVE-2026-104252 critical 9.8 1% 2026
CVE-2026-27969 high 8.8 0% 2026
CVE-2026-65959 medium 5.3 0% 2026
CVE-2023-29195 medium 4.1 1% 2023
CVE-2023-29194 medium 4.1 1% 2023

Is my Vitess version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Vitess version → · Monitor Vitess for new CVEs →

Vitess vulnerabilities — frequently asked

How many known vulnerabilities does Vitess have?

IsItPatched tracks 6 CVEs for Vitess. 2 are critical-severity and 1 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Vitess have any actively-exploited vulnerabilities?

None of Vitess's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Vitess vulnerability?

Among tracked issues, CVE-2026-27965 (CRITICAL, CVSS 9.9) ranks highest — a OS command injection weakness.

Is Vitess safe to use?

It depends on the version. The latest supported Vitess release (24.0.5) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Vitess security status · Vitess end-of-life · actively-exploited CVEs. Always verify against CNCF's advisories — see our disclaimer.