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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:L/SC:L/SI:H/SA:H · score source

EPSS

• CVE-2026-27969: 0.54% estimated exploitation activity in the next 30 days; percentile 45.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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/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. Patches v23.0.3 and v22.0.4 Resources https://github.com/vitessio/vitess/pull/19470

Published by the source

27 Feb 2026, 16:03 UTC

Last modified by the source

27 Feb 2026, 16:03 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-r492-hjgh-c9gw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27969

Advisory: Vitess users with backup storage access can write to arbitrary file paths on restore
IDs: CVE-2026-27969, GHSA-r492-hjgh-c9gw
Record: https://patchnext.com/advisories/cve-2026-27969 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vitess.io/vitess 0.23.3, 0.22.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go vitess.io/vitess: affected >= 0.23.0-rc1, < 0.23.3; < 0.22.4; fixed in 0.22.4, 0.23.3

## Suggested inspection (read-only)
- Go vitess.io/vitess: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vitess.io/vitess.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r492-hjgh-c9gw (GitHub-reviewed advisory GHSA-r492-hjgh-c9gw lists affected ranges: Go vitess.io/vitess >=0.23.0-rc1 =0 <0.22.4)

Commands are suggestions: review each one before running it.