CVE-2026-32637

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
42
EG Risk 42/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 20, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit c7fa4bfe3571 (velero-io/velero)

Fix landed in velero-io/velero commit c7fa4bfe3571 — awaiting tagged release

https://github.com/velero-io/velero/commit/c7fa4bfe3571667e9731f3f504da3c6be709a24c
github_commit

commit 3f8e35884963 (velero-io/velero)

Fix landed in velero-io/velero commit 3f8e35884963 — awaiting tagged release

https://github.com/velero-io/velero/commit/3f8e3588496391979915ace065f732a9013c1cf0
generic

Can anyone explain to me what the purpose of the G305 rule is? And how to improve it, thank you · Issue #324 · securego/gosec · GitHub

https://github.com/securego/gosec/issues/324
githubMentions a patch (unverified)🟡 PoC Available

File path traversal when extracting from backup's tarball · Advisory · velero-io/velero · GitHub

https://github.com/velero-io/velero/security/advisories/GHSA-j2g6-362q-6qc6

Vendor Advisories for CVE-2026-32637(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/vmware-tanzu/velero—
  • every version up to 1.18.1: fixed in 1.18.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-08 05:23 UTCEG score recompute
  5. 2026-10-07 23:47 UTCEPSS rescore
  6. 2026-10-07 03:49 UTCEG score recompute
  7. 2026-10-06 15:17 UTCEPSS rescore
  8. 2026-10-06 03:27 UTCEG score recompute
  9. 2026-10-05 17:42 UTCEPSS rescore
  10. 2026-10-04 23:22 UTCEPSS rescore
  11. 2026-10-03 16:47 UTCEG score recompute
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-02 09:12 UTCEG score recompute
  14. 2026-10-01 19:49 UTCEPSS rescore
  15. 2026-10-01 08:36 UTCEG score recompute
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-30 08:14 UTCEG score recompute
  18. 2026-09-29 03:44 UTCEG score recompute
  19. 2026-09-28 13:51 UTCEPSS rescore
  20. 2026-09-28 03:17 UTCEG score recompute
  21. 2026-09-27 13:48 UTCEPSS rescore
  22. 2026-09-27 03:03 UTCEG score recompute
  23. 2026-09-26 15:58 UTCEPSS rescore
  24. 2026-09-26 00:26 UTCEPSS rescore
  25. 2026-09-25 02:00 UTCEG score recompute
Show 53 more
  1. 2026-09-24 01:44 UTCEG score recompute
  2. 2026-09-23 01:29 UTCEG score recompute
  3. 2026-09-22 01:14 UTCEG score recompute
  4. 2026-09-21 00:58 UTCEG score recompute
  5. 2026-09-20 20:15 UTCEPSS rescore
  6. 2026-09-20 00:43 UTCEG score recompute
  7. 2026-09-19 00:28 UTCEG score recompute
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-18 19:27 UTCEPSS rescore
  10. 2026-09-18 00:11 UTCEG score recompute
  11. 2026-09-17 19:30 UTCEPSS rescore
  12. 2026-09-16 23:56 UTCEG score recompute
  13. 2026-09-16 14:08 UTCEPSS rescore
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 23:40 UTCEG score recompute
  16. 2026-09-13 22:27 UTCEG score recompute
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-12 22:12 UTCEG score recompute
  19. 2026-09-12 15:01 UTCEPSS rescore
  20. 2026-09-11 21:57 UTCEG score recompute
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-10 21:41 UTCEG score recompute
  23. 2026-09-10 09:34 UTCEPSS rescore
  24. 2026-09-09 03:13 UTCEG score recompute
  25. 2026-09-08 22:00 UTCEPSS rescore
  26. 2026-09-08 02:58 UTCEG score recompute
  27. 2026-09-07 16:01 UTCEPSS rescore
  28. 2026-09-07 02:43 UTCEG score recompute
  29. 2026-09-06 13:47 UTCEPSS rescore
  30. 2026-09-06 13:47 UTCEPSS rescore
  31. 2026-09-06 01:44 UTCEG score recompute
  32. 2026-09-05 01:27 UTCEG score recompute
  33. 2026-09-04 05:06 UTCEPSS rescore
  34. 2026-09-03 00:56 UTCEG score recompute
  35. 2026-09-02 14:11 UTCEPSS rescore
  36. 2026-09-02 00:34 UTCEG score recompute
  37. 2026-09-01 13:53 UTCEPSS rescore
  38. 2026-09-01 04:39 UTCEPSS rescore
  39. 2026-09-01 04:39 UTCEPSS rescore
  40. 2026-08-30 23:58 UTCEG score recompute
  41. 2026-08-30 19:17 UTCEPSS rescore
  42. 2026-08-30 01:22 UTCEPSS rescore
  43. 2026-08-28 23:28 UTCEG score recompute
  44. 2026-08-28 22:51 UTCEG score recompute
  45. 2026-08-28 21:41 UTCEPSS rescore
  46. 2026-08-27 23:00 UTCEG score recompute
  47. 2026-08-27 14:25 UTCEPSS rescore
  48. 2026-08-26 22:45 UTCEG score recompute
  49. 2026-08-26 14:46 UTCEPSS rescore
  50. 2026-08-25 22:29 UTCEG score recompute
  51. 2026-08-25 21:25 UTCEG score recompute▲ 5.90
  52. 2026-08-25 21:24 UTCMITRE cvelistV5CVSS v3 → 5.9 · CVSS v4 → 5.9
  53. 2026-08-20 17:42 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-32637?
CVE-2026-32637 is a medium vulnerability published on August 20, 2026. 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…
When was CVE-2026-32637 disclosed?
CVE-2026-32637 was first published on August 20, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32637 actively exploited?
CVE-2026-32637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32637?
CVE-2026-32637 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32637?
A fix for CVE-2026-32637 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32637 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32637

Explore →

Is Your Infrastructure Affected by CVE-2026-32637?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.