CVE-2026-32637: Github.com/vmware tanzu/velero Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-j2g6-362q-6qc6
CWE-22
Published
Advisory Summary

CVE-2026-32637 is a MODERATE path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Github.com/vmware tanzu/velero libraries in the Go ecosystem. The issue involves velero vulnerable to file path traversal when extracting from backup's tarball. Remediation is available by upgrading affected packages to version 1.18.1.

CVE-2026-32637 at a Glance

CVE Identifier CVE-2026-32637
GHSA Identifier GHSA-j2g6-362q-6qc6
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Github.com/vmware tanzu/velero
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-32637

To remediate this vulnerability, upgrade all affected Github.com/vmware tanzu/velero dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/vmware-tanzu/velero fixed: 1.18.1
Upgrade github.com/vmware-tanzu/velero to 1.18.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/vmware-tanzu/velero

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-32637, inspect your project dependencies for Github.com/vmware tanzu/velero:

inspect dependencies for github.com/vmware-tanzu/velero

Analyze the terminal output to locate any version of Github.com/vmware tanzu/velero in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.18.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Github.com/vmware tanzu/velero, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact _What kind of vulnerability is it? Who is impacted?_ If the attacker compromises the backup's object storage backend and uploads a malicious backup tarball including file names like the following: * ../../../tmp/escape_1 -> file created at /tmp/escape_1 * ../../../../../../../../tmp/escape_2 -> file created at /tmp/escape_2 * ../../../tmp/cron_poc -> would be /etc/cron.d/backdoor in real attack * ../../../tmp/ssh_poc -> would be ~/.ssh/authorized_keys * ../../../tmp/kubeconfig_poc -> would be ~/.kube/config It's possible that extracting files from the tarball during restore can overwrite sensitive files in the Velero pod filesystem. ### Patches _Has the problem been patched? What versions should users upgrade to?_ By far, there is no patch yet. We are working on the main branch, then cherry-pick to the release-1.18 for v1.18.1 patch. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ There is no workaround, but the good news is that keeping your OSS safe will prevent the vulnerability.

CVE-2026-32637 Affected Github.com/vmware tanzu/velero Versions

1 component(s)
Fixed Versions:
1.18.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/vmware-tanzu/velero
Go
< 1.18.1
1.18.1

References

Frequently Asked Questions

What is CVE-2026-32637?
CVE-2026-32637 is a security vulnerability in Github.com/vmware tanzu/velero involving Velero vulnerable to file path traversal when extracting from backup's tarball under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Github.com/vmware tanzu/velero versions are affected?
Affected versions include releases prior to 1.18.1 across affected packages: github.com/vmware-tanzu/velero.
What version fixes CVE-2026-32637?
Upgrading to 1.18.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/vmware-tanzu/velero affected?
Yes, github.com/vmware-tanzu/velero is affected in releases prior to 1.18.1. Upgrade your dependency to 1.18.1 or later.
What CWE is associated with CVE-2026-32637?
CVE-2026-32637 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check Go dependencies for CVE-2026-32637?
Run the dependency tree command: 'inspect dependencies for github.com/vmware-tanzu/velero'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-j2g6-362q-6qc6",
  "modified" : "2026-08-20T17:26:08Z",
  "published" : "2026-08-20T17:26:07Z",
  "aliases" : [ "CVE-2026-32637" ],
  "summary" : "Velero vulnerable to file path traversal when extracting from backup's tarball",
  "details" : "### Impact\n_What kind of vulnerability is it? Who is impacted?_\nIf the attacker compromises the backup's object storage backend and uploads a malicious backup tarball including file names like the following:\n* ../../../tmp/escape_1              -> file created at /tmp/escape_1\n* ../../../../../../../../tmp/escape_2 -> file created at /tmp/escape_2\n* ../../../tmp/cron_poc              -> would be /etc/cron.d/backdoor in real attack\n* ../../../tmp/ssh_poc               -> would be ~/.ssh/authorized_keys\n* ../../../tmp/kubeconfig_poc        -> would be ~/.kube/config\n\nIt's possible that extracting files from the tarball during restore can overwrite sensitive files in the Velero pod filesystem. \n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nBy far, there is no patch yet.\nWe are working on the main branch, then cherry-pick to the release-1.18 for v1.18.1 patch.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nThere is no workaround, but the good news is that keeping your OSS safe will prevent the vulnerability.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/vmware-tanzu/velero"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.18.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/velero-io/velero/security/advisories/GHSA-j2g6-362q-6qc6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/securego/gosec/issues/324"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/velero-io/velero"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-20T17:26:07Z",
    "nvd_published_at" : null
  }
}