CVE-2025-62878: SUSE Rancher · Relative Path Traversal
Affects SUSE RancherSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical : upgrade to 0.0.34 as a priority.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.0.34
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Rancher and github.com/rancher/local-path-provisioner to 0.0.34.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SUSERancher | Affected
| Fixed in
|
GitHubgithub.com/rancher/local-path-provisionerpkg:github/github.com/rancher/local-path-provisionerOther threats | Affected
| Fixed in
|
GitHubrancher/rancherpkg:github/rancher/rancherOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-62878, organizations should immediately apply any patches or updates released by SUSE addressing this vulnerability once available. In the absence of patches, restrict access to Rancher's API and management interfaces to trusted administrators only, employing network segmentation and strict access controls. Implement runtime monitoring and file integrity checks on host nodes to detect unauthorized file modifications. Review and harden PersistentVolume creation policies to enforce strict path validation and limit volume mounts to predefined safe directories. Employ container security best practices such as least privilege principles for Rancher users and service accounts. Additionally, consider deploying host-based intrusion detection systems (HIDS) to alert on suspicious file system activities. Regularly audit Rancher configurations and logs for anomalous volume creation requests. Finally, maintain an incident response plan tailored to container orchestration environments to quickly respond to potential exploitation.
Description
A malicious user can manipulate the parameters.pathPattern to create PersistentVolumes in arbitrary locations on the host node, potentially overwriting sensitive files or gaining access to unintended directories.