Skip to main content
VulnerabilityPublished

CVE-2026-27965: vitessio vitess · OS Command Injection

Affects vitessio vitessSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High : upgrade to 23.0.3 or 22.0.4 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 23.0.3, 22.0.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade vitess to 23.0.3 or 22.0.4; vitessio/vitess to 22.0.4.

Affected software

ProductAffectedFixed in
vitessiovitessAffected
  • >=23.0.0 <23.0.3
Fixed in
  • 23.0.3
vitessiovitessAffected
  • <22.0.4
Fixed in
  • 22.0.4
GitHubvitessio/vitesspkg:github/vitessio/vitessOther threatsAffected
  • <22.0.4
Fixed in
  • 22.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Upgrade Vitess to version 22.0.4 or 23.0.3 or later, where the vulnerability is patched.
  2. Restrict access to backup storage locations (e.g., S3 buckets) to trusted personnel and systems only, enforcing strict IAM policies and network controls to prevent unauthorized read/write access.
  3. Use the --external-decompressor flag in vttablet and vtbackup to specify a safe decompressor command such as 'cat' or 'tee' if no external decompressor is required, thereby overriding any potentially malicious commands in the manifest files.
  4. Regularly audit backup storage contents and access logs to detect unauthorized modifications or access attempts.
  5. Implement monitoring and alerting on backup restoration activities to detect anomalous behavior.
  6. Consider isolating backup restoration environments to minimize the impact of potential exploitation.
  7. Educate administrators on the risks of trusting backup manifests and the importance of secure backup storage configurations. These steps go beyond generic patching by emphasizing secure backup storage management and safe configuration of decompression commands.

Description

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 any additional arbitrary commands there. Versions 23.0.3 and 22.0.4 contain a patch. Some workarounds are available. Those who intended to use an external decompressor then can always specify that decompressor command in the `--external-decompressor` flag value for `vttablet` and `vtbackup`. That then overrides any value specified in the manifest file. Those who did not intend to use an external decompressor, nor an internal one, can specify a value such as `cat` or `tee` in the `--external-decompressor` flag value for `vttablet` and `vtbackup` to ensure that a harmless command is always used.

References

Community reviews

Loading reviews…