Is vitess.io/vitess 0.22 vulnerable?

Go · 5 releases from 0.22.0 to 0.22.4 · latest vitess.io/vitess is 0.24.5 · checked 18 Nov 2026

Yes: 5 known advisories

Yes. vitess.io/vitess 0.22.4, the last 0.22 release, is affected by 5 known security advisories (1 critical, 1 high, 1 medium, 2 low), including CVE-2026-104252, CVE-2026-27965, CVE-2026-65959. 3 more affect earlier 0.22.x releases. At least one has no fixed release yet.

Is your project on an affected vitess.io/vitess?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting vitess.io/vitess 0.22.4

  • LowCVE-2026-104252GO-2026-67985 Nov 2026

    Vitess vttablet /twopcz reflected XSS in vitess.io/vitess

    Affected
    <0.23.5 · >=0.24.0 <0.24.2
    Fixed in
    0.23.5, 0.24.2
  • CriticalCVE-2026-104252GHSA-v75v-6fpf-gvw815 Oct 2026

    Vitess vttablet /twopcz reflected XSS

    Affected
    <0.23.5 · >=0.24.0 <0.24.2
    Fixed in
    0.23.5, 0.24.2
  • LowCVE-2026-65959GO-2026-635615 Sept 2026

    Missing authorization on vttablet /debug/vrlog in vitess.io/vitess

    Affected
    <0.23.6 · >=0.24.0-rc1 <0.24.3
    Fixed in
    0.23.6, 0.24.3
  • MediumCVE-2026-65959GHSA-mhc4-g3wh-cw7m18 Aug 2026

    Vitess: Missing authorization on vttablet /debug/vrlog exposes live VReplication SQL data

    Affected
    >=0.24.0-rc1 <=0.24.2 · <=0.23.6
    Fixed in
    No fix released
  • HighCVE-2026-27965GHSA-8g8j-r87h-p36x26 Feb 2026

    Vitess users with backup storage access can gain unauthorized access to production deployment environments

    Affected
    <=0.23.2
    Fixed in
    No fix released

Fixed within 0.22.x, affecting earlier releases

  • LowCVE-2026-27965GO-2026-456710 Mar 2026

    Vitess users can gain unauthorized access to production deployment environments in vitess.io/vitess

    Affected
    <0.22.4 · >=0.23.0 <0.23.3
    Fixed in
    0.22.4, 0.23.3
  • LowCVE-2026-27969GO-2026-457010 Mar 2026

    Vitess users with backup storage access can write to arbitrary file paths in vitess.io/vitess

    Affected
    <0.22.4 · >=0.23.0-rc1 <0.23.3
    Fixed in
    0.22.4, 0.23.3
  • CriticalCVE-2026-27969GHSA-r492-hjgh-c9gw27 Feb 2026

    Vitess users with backup storage access can write to arbitrary file paths on restore

    Affected
    >=0.23.0-rc1 <0.23.3 · <0.22.4
    Fixed in
    0.22.4, 0.23.3

Every vitess.io/vitess 0.22.x release

Affected: 0.22.0 to 0.22.4. Latest vitess.io/vitess: 0.24.5.

VersionKnown advisories
vitess.io/vitess 0.22.4CVE-2026-104252, CVE-2026-104252, CVE-2026-65959, CVE-2026-65959, CVE-2026-27965
vitess.io/vitess 0.22.3CVE-2026-104252, CVE-2026-104252, CVE-2026-65959, CVE-2026-65959, CVE-2026-27965, CVE-2026-27969, CVE-2026-27969, CVE-2026-27965
vitess.io/vitess 0.22.2CVE-2026-104252, CVE-2026-104252, CVE-2026-65959, CVE-2026-65959, CVE-2026-27965, CVE-2026-27969, CVE-2026-27969, CVE-2026-27965
vitess.io/vitess 0.22.1CVE-2026-104252, CVE-2026-104252, CVE-2026-65959, CVE-2026-65959, CVE-2026-27965, CVE-2026-27969, CVE-2026-27969, CVE-2026-27965
vitess.io/vitess 0.22.0CVE-2026-104252, CVE-2026-104252, CVE-2026-65959, CVE-2026-65959, CVE-2026-27965, CVE-2026-27969, CVE-2026-27969, CVE-2026-27965

Which of your client projects are still on vitess.io/vitess 0.22?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact vitess.io/vitess version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other vitess.io/vitess versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.