Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Velero vulnerable to file path traversal when extracting from backup's tarball

CVE-2026-32637GHSA-j2g6-362q-6qc6

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/vmware-tanzu/velero 1.18.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · 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 · score source
EPSS
  • CVE-2026-32637: 0.54% estimated exploitation activity in the next 30 days; percentile 45.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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/escape1 - file created at /tmp/escape1 ../../../../../../../../tmp/escape2 - file created at /tmp/escape2 ../../../tmp/cronpoc - would be /etc/cron.d/backdoor in real attack ../../../tmp/sshpoc - would be ~/.ssh/authorizedkeys ../../../tmp/kubeconfigpoc - 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-j2g6-362q-6qc6

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6259

  4. Revision 1 · created ·

    Published from osv record GHSA-j2g6-362q-6qc6

Agent brief

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

# Patch Next advisory brief: CVE-2026-32637

Advisory: Velero vulnerable to file path traversal when extracting from backup's tarball
IDs: CVE-2026-32637, GHSA-j2g6-362q-6qc6
Record: https://patchnext.com/advisories/cve-2026-32637 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/vmware-tanzu/velero 1.18.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/vmware-tanzu/velero: affected < 1.18.1; fixed in 1.18.1

## Suggested inspection (read-only)
- Go github.com/vmware-tanzu/velero: 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 github.com/vmware-tanzu/velero.
- 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://osv.dev/vulnerability/GHSA-j2g6-362q-6qc6 (OSV record GHSA-j2g6-362q-6qc6 lists affected ranges: Go github.com/vmware-tanzu/velero >=0 <1.18.1 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6259 (OSV record GO-2026-6259 lists affected ranges: Go github.com/vmware-tanzu/velero >=0 <1.18.1 (fixed))
- Verified: https://github.com/advisories/GHSA-j2g6-362q-6qc6 (GitHub-reviewed advisory GHSA-j2g6-362q-6qc6 lists affected ranges: Go github.com/vmware-tanzu/velero >=0 <1.18.1)

Commands are suggestions: review each one before running it.

Loading voting…