How severe is CVE-2026-32637?

No CVSS score has been assigned to CVE-2026-32637 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32637?

CVE-2026-32637 affects the following packages: github.com/vmware-tanzu/velero (Go). Ecosystems affected: Go.

How do I fix CVE-2026-32637?

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.

How do I detect CVE-2026-32637 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/vmware-tanzu/velero, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-32637 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-32637 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32637 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-32637?

CVE-2026-32637 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-32637?

CVE-2026-32637 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-32637 published, and has it been updated?

CVE-2026-32637 was published on August 25, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-32637 — velero

Fix: velero-io/velero@3f8e358

CVE-2026-32637 is a Path Traversal vulnerability in github.com/vmware-tanzu/velero. A fix is available for github.com/vmware-tanzu/velero — see the affected versions and patch details below.

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

Also known asGHSA-j2g6-362q-6qc6GO-2026-6259

Published

Aug 25, 2026

Updated

Sep 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32637.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/vmware-tanzu/velero

Real-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

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/vmware-tanzu/velero`	all versions	1.18.1`go get github.com/vmware-tanzu/velero@v1.18.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/vmware-tanzu/velero, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2026-32637 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works