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.
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.
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.
### 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.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Aug 25, 2026, 9:15:31 PM
dateUpdated: Aug 28, 2026, 10:38:21 PM
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-22
Original publisher date fields
published: 2026-08-25T22:17:02.380
lastModified: 2026-09-09T21:09:13.080
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.