Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Check if your repositories are affected!View on GitHub
Search

GHSA-j2g6-362q-6qc6

MediumCVSS 6.9 / 10
Published Aug 20, 2026·Last modified Aug 20, 2026
Affected Components(1)
Go logogithub.com/vmware-tanzu/velero
< 1.18.1
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.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
6.9

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
2.7

Limited exploitation activity has been observed. Close monitoring and planned remediation are recommended.

EPSS
0.51%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard