LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27969: Vitess users with backup storage access can write to arbitrary file paths on restore

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 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. Versions 23.0.3 and 22.0.4 contain a patch. No known workarounds are available.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-27969 affects Vitess restore operations. If someone can read and write the backup storage location, they can tamper with backup manifests so restore writes files outside intended paths. That could give unintended access to the production environment and enable arbitrary command execution. Patched versions are 22.0.4 and 23.0.3.

Executive priority

Prioritize quickly for Vitess environments with cloud or shared backup storage. The vulnerability is critical because backup tampering can cross into production during restore. Organizations not running Vitess, not using affected versions, or tightly controlling backup write access have lower immediate exposure.

Technical view

Vitess before 22.0.4 and 23.0.3 has a CWE-22 path traversal issue in backup restore handling. A high-privilege actor with backup storage read/write access can manipulate manifest file paths, causing restore to write attacker-controlled backup contents to arbitrary accessible locations. CVSS v4.0 is 9.3 critical.

Likely exposure

Exposure is limited to Vitess deployments using affected versions and backup storage where an actor has read/write access. Risk is highest where backup storage permissions are broad, shared, or accessible from compromised CI/CD, cloud, or operations accounts.

Exploitation context

The advisory requires backup storage read/write access and a restore action, with user interaction noted in the CVSS vector. The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Successful abuse could affect confidentiality, integrity, and availability of the production environment.

Researcher notes

Key constraints matter: the attacker needs read/write access to backup storage and a restore path must process the manipulated manifest. Sources state no known workarounds and identify patches in 22.0.4 and 23.0.3. Do not assume internet-exploitable exposure without evidence of exposed backup storage access.

Mitigation direction

  • Upgrade Vitess 22.x to 22.0.4 or later.
  • Upgrade Vitess 23.x to 23.0.3 or later.
  • Restrict backup storage read/write permissions to trusted restore processes.
  • Review vendor advisory for any updated operational guidance.
  • Treat backup storage credentials as sensitive production-impacting secrets.

Validation and detection

  • Inventory Vitess versions across production, staging, and disaster recovery environments.
  • Identify deployments using versions before 22.0.4 or 23.0.3.
  • Review who or what has write access to Vitess backup storage.
  • Check recent restore activity for unexpected timing or operators.
  • Confirm restored systems are running patched Vitess versions after remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27969 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:H/VA:L/SC:L/SI:H/SA:H——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-27969Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
vitessiovitess< 22.0.4, >= 23.0.0, < 23.0.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.