VulnerabilityPublished 4 Mar 2026

CVE-2025-62879: SUSE Rancher · Sensitive Data in Logs

Affects SUSE RancherSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.8 Medium · fixed in 9.0.1 : update SUSE Rancher when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.0.1, 8.1.2, 7.0.5 +1

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Rancher and github.com/rancher/backup-restore-operator to 9.0.1, 8.1.2, 7.0.5 or 6.0.3.

Affected software

Product	Affected	Fixed in
SUSERancher	Affected >=9.0.0 <9.0.1	Fixed in 9.0.1
SUSERancher	Affected >=8.0.0 <8.1.2	Fixed in 8.1.2
SUSERancher	Affected >=7.0.0 <7.0.5	Fixed in 7.0.5
SUSERancher	Affected >=6.0.0 <6.0.3	Fixed in 6.0.3
GitHubgithub.com/rancher/backup-restore-operator`pkg:github/github.com/rancher/backup-restore-operator`Other threats	Affected >=9.0.0 <9.0.1 >=8.0.0 <8.1.2 >=7.0.0 <7.0.5 >=6.0.0 <6.0.3	Fixed in 9.0.1 8.1.2 7.0.5 6.0.3
GitHubrancher/rancher`pkg:github/rancher/rancher`Other threats	Affected 6.0.0 – 9.0.0 4 affected builds	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-62879, organizations should implement the following specific actions: 1) Immediately restrict access to rancher-backup-operator pod logs to only trusted administrators and systems to minimize exposure. 2) Rotate all S3 accessKey and secretKey credentials that may have been logged to invalidate any potentially compromised tokens. 3) Implement strict role-based access control (RBAC) within Kubernetes and Rancher to limit who can view pod logs and access backup operator components. 4) Monitor logs and cloud storage access patterns for unusual or unauthorized activity that may indicate credential misuse. 5) Review and sanitize logging configurations in Rancher and the backup operator to prevent sensitive information from being logged in the future. 7) Consider using dedicated secrets management solutions integrated with Rancher to avoid embedding sensitive credentials in logs or configuration files. 8) Conduct regular security audits of Kubernetes clusters and backup operations to detect and remediate similar information exposure issues proactively.

Description

A vulnerability has been identified within the Rancher Backup Operator, resulting in the leakage of S3 tokens (both accessKey and secretKey) into the rancher-backup-operator pod's logs.

Impact

The primary impact of CVE-2025-62879 is the compromise of confidentiality through the exposure of S3 access credentials in log files. If an attacker or unauthorized user gains access to these logs, they can retrieve the accessKey and secretKey, enabling them to access, modify, or delete data stored in the associated S3 buckets. This could lead to data breaches, data loss, or unauthorized data manipulation. Since Rancher is widely used for Kubernetes cluster management and backup operations, the exposure of backup credentials can also jeopardize the integrity of backup data and disaster recovery processes indirectly. Although exploitation requires privileged access to the operator pod logs, insider threats or attackers who have already gained elevated privileges could leverage this vulnerability to escalate their access to cloud storage resources. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially in environments with lax access controls or insufficient log management. Organizations relying on Rancher for cloud-native infrastructure management and backup are particularly vulnerable, and the impact extends to any business-critical data stored in S3-compatible storage systems.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Mar 2026, 15:32 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats