Summary
Vitess users with backup storage access can write to arbitrary file paths on restore
Resources
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
v23.0.3 and v22.0.4
Frequently Asked Questions
- What is CVE-2026-27969? CVE-2026-27969 is a critical-severity path traversal vulnerability in vitess.io/vitess (go), affecting versions >= 0.23.0-rc1, < 0.23.3. It is fixed in 0.23.3, 0.22.4. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of vitess.io/vitess are affected by CVE-2026-27969? vitess.io/vitess (go) versions >= 0.23.0-rc1, < 0.23.3 is affected.
- Is there a fix for CVE-2026-27969? Yes. CVE-2026-27969 is fixed in 0.23.3, 0.22.4. Upgrade to this version or later.
- Is CVE-2026-27969 exploitable, and should I be worried? Whether CVE-2026-27969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-27969 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-27969?
- Upgrade
vitess.io/vitessto 0.23.3 or later - Upgrade
vitess.io/vitessto 0.22.4 or later
- Upgrade