{"answers":{"affected":"3 open source packages ship an affected version, including github.com/vmware-tanzu/velero.","exploited":"There is no known exploitation of CVE-2026-32637 in the wild and no public exploit code.","fix":"Upgrade github.com/vmware-tanzu/velero to 1.18.1 or later.","what":"CVE-2026-32637 is a medium-severity path traversal vulnerability in velero-io velero, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32637 and fix it if it is affected.\n\nWhat it is: CVE-2026-32637 is a medium-severity path traversal vulnerability in velero-io velero, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32637 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/vmware-tanzu/velero (Go): affected all versions; fixed in 1.18.1\n- github.com/vmware-tanzu/velero (Go): affected all versions; fixed in 1.18.1\n- github.com/vmware-tanzu/velero (Go): affected all versions; fixed in 1.18.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32637/ (Markdown: https://insights.sbomify.com/CVE-2026-32637/index.md)","id":"CVE-2026-32637","markdown":"https://insights.sbomify.com/CVE-2026-32637/index.md","name":"CVE-2026-32637","record":{"aliases":["CLEANSTART-2026-ZM91804","GHSA-j2g6-362q-6qc6","GO-2026-6259","MINI-33x3-j7rp-j6hp","MINI-3m3p-xqx3-m69p","MINI-3xq2-jjf5-4crj","MINI-695x-6c52-56wg","MINI-7357-mj4h-wxpv","MINI-c888-42pc-2wfh","MINI-f92j-w67m-jh6c","MINI-g25c-mmhq-pp7m","MINI-g7gj-865m-rphp","MINI-g8j4-gf3f-hmhc","MINI-gp9f-6635-xjm7","MINI-jmm6-5h98-hhjx","MINI-m5r3-2rhf-grgx","MINI-q78v-4gq5-7jj7","MINI-vj96-r8vh-rx2p","MINI-xrp6-3v36-7xvv"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes backup tool","requires_auth":"none","summary":"An attacker with access to the backup storage can upload a malicious tarball to overwrite files in the Velero pod during restore.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Velero vulnerable to file path traversal when extracting from backup's tarball","id":"CVE-2026-32637","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens","id":"CVE-2026-32638"},"packages":[{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/vmware-tanzu/velero","purl":null,"source":"GHSA-j2g6-362q-6qc6"},{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/vmware-tanzu/velero","purl":"pkg:golang/github.com/vmware-tanzu/velero","source":"GHSA-j2g6-362q-6qc6"},{"ecosystem":"Go","fixed":["1.18.1"],"introduced":["0"],"last_affected":[],"package":"github.com/vmware-tanzu/velero","purl":"pkg:golang/github.com/vmware-tanzu/velero","source":"GO-2026-6259"}],"prev":{"headline":"ImageMagick has a heap-buffer-overflow in NewXMLTree which could result in crash","id":"CVE-2026-32636"},"products":["velero"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["velero-io"]},"summary":"An attacker with access to the backup storage can upload a malicious tarball to overwrite files in the Velero pod during restore.","url":"https://insights.sbomify.com/CVE-2026-32637/"}