CVE-2026-32637
CVE-2026-32637 is a security vulnerability in github.com/vmware-tanzu/velero. O3 Security confirms whether CVE-2026-32637 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Velero vulnerable to file path traversal when extracting from backup's tarball
Real-World Exposure
github.com/vmware-tanzu/veleroReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/vmware-tanzu/velero | all versions | 1.18.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/vmware-tanzu/velero. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/vmware-tanzu/velero to 1.18.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32637 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-32637 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-32637. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32637 in your dependencies?
O3 detects CVE-2026-32637 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.