Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 4.0 5.9 MEDIUMEUVD CVSS 4.0 5.9 CVSS 4.0 · [email protected] · Secondary 5.9 MEDIUMCVSS_V4 Publisher rating MODERATEFixed by github.com/vmware-tanzu/velero 1.18.1osv · severity unknownFixed by github.com/vmware-tanzu/velero 1.18.1KEV status unknown

cve-program · CVE-2026-32637

Published

Velero is an open source tool for backing up, restoring, and migrating Kubernetes cluster resources and persistent volumes. Prior to 1.18.1, an attacker who compromises the backup object-storage backend can upload a malicious backup tarball containing parent-directory paths that escape the extraction directory during restore and overwrite sensitive files in the Velero pod filesystem. This issue is fixed in version 1.18.1.

Read the publisher's advisory

euvd · EUVD-2026-66117

Published

Velero is an open source tool for backing up, restoring, and migrating Kubernetes cluster resources and persistent volumes. Prior to 1.18.1, an attacker who compromises the backup object-storage backend can upload a malicious backup tarball containing parent-directory paths that escape the extraction directory during restore and overwrite sensitive files in the Velero pod filesystem. This issue is fixed in version 1.18.1.

Read the publisher's advisory

nvd · CVE-2026-32637

Published

Velero is an open source tool for backing up, restoring, and migrating Kubernetes cluster resources and persistent volumes. Prior to 1.18.1, an attacker who compromises the backup object-storage backend can upload a malicious backup tarball containing parent-directory paths that escape the extraction directory during restore and overwrite sensitive files in the Velero pod filesystem. This issue is fixed in version 1.18.1.

Read the publisher's advisory

osv · GHSA-j2g6-362q-6qc6

Published

### 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.

Read the publisher's advisory

osv · GO-2026-6259

Published

Velero vulnerable to file path traversal when extracting from backup's tarball in github.com/vmware-tanzu/velero

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-32637 · CVE overview and exploitation status

EUVD-2026-66117

GHSA-j2g6-362q-6qc6

GO-2026-6259

cve-program · CVE-2026-32637

euvd · EUVD-2026-66117

nvd · CVE-2026-32637

osv · GHSA-j2g6-362q-6qc6

osv · GO-2026-6259

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 07:54 UTC · 270 of 275 readable · 255 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current