CVE-2025-62879
published 2026-03-04CVE-2025-62879: A vulnerability has been identified within the Rancher Backup Operator, resulting in the leakage of S3 tokens (both accessKey and secretKey) into the…
PriorityP426medium4.9CVSS 3.1
AVNACLPRHUINSUCHINAN
EPSS
0.34%
26.5th percentile
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.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | rancher_backup-restore-operator | >= 6.0.0 < 6.0.3 | 6.0.3 |
| github.com | rancher_backup-restore-operator | >= 7.0.0 < 7.0.5 | 7.0.5 |
| github.com | rancher_backup-restore-operator | >= 8.0.0 < 8.1.2 | 8.1.2 |
| github.com | rancher_backup-restore-operator | >= 9.0.0 < 9.0.1 | 9.0.1 |
| suse | rancher | >= 6.0.0 < 6.0.3 | 6.0.3 |
| suse | rancher | >= 7.0.0 < 7.0.5 | 7.0.5 |
| suse | rancher | >= 8.0.0 < 8.1.2 | 8.1.2 |
| suse | rancher | >= 9.0.0 < 9.0.1 | 9.0.1 |
| suse | rancher_backup_and_restore_operator | >= 6.0.0 < 6.0.3 | 6.0.3 |
| suse | rancher_backup_and_restore_operator | >= 7.0.0 < 7.0.5 | 7.0.5 |
| suse | rancher_backup_and_restore_operator | >= 8.0.0 < 8.1.2 | 8.1.2 |
| suse | rancher_backup_and_restore_operator | >= 9.0.0 < 9.0.1 | 9.0.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Rancher Backup Operator pod's logs leak S3 tokens in github.com/rancher/backup-restore-operator
osv·2026-03-10
CVE-2025-62879 Rancher Backup Operator pod's logs leak S3 tokens in github.com/rancher/backup-restore-operator
Rancher Backup Operator pod's logs leak S3 tokens in github.com/rancher/backup-restore-operator
Rancher Backup Operator pod's logs leak S3 tokens in github.com/rancher/backup-restore-operator.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/rancher/backup-restore-operator from v6.0.0 before v6.0.3, from v7.0.0 before v7.0.5, from v8.0.0 before v8.1.2, from v9.0.0 before v9.0.1.
GHSA
Rancher Backup Operator pod's logs leak S3 tokens
ghsa·2026-03-03
CVE-2025-62879 [MEDIUM] CWE-532 Rancher Backup Operator pod's logs leak S3 tokens
Rancher Backup Operator pod's logs leak S3 tokens
### Impact
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.
Specifically, the S3 `accessKey` and `secretKey` are exposed in the pod's logs under the following logging level conditions:
| Variable Exposed | Logging Level Condition |
------------------ | ------------------------- |
| accessKey | `trace: false` (default), and `debug: false` (default) |
| secretKey | `trace: true` or `debug: true`|
**Note:** The S3 `accessKey` is exposed in the logs without requiring any supplementary configuration.
For further information on this attack category, please consult the associated [MITRE ATT&CK - Techniqu
OSV
Rancher Backup Operator pod's logs leak S3 tokens
osv·2026-03-03
CVE-2025-62879 [MEDIUM] Rancher Backup Operator pod's logs leak S3 tokens
Rancher Backup Operator pod's logs leak S3 tokens
### Impact
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.
Specifically, the S3 `accessKey` and `secretKey` are exposed in the pod's logs under the following logging level conditions:
| Variable Exposed | Logging Level Condition |
------------------ | ------------------------- |
| accessKey | `trace: false` (default), and `debug: false` (default) |
| secretKey | `trace: true` or `debug: true`|
**Note:** The S3 `accessKey` is exposed in the logs without requiring any supplementary configuration.
For further information on this attack category, please consult the associated [MITRE ATT&CK - Techniqu
No detection rules found.
No public exploits indexed.
2026-03-04
Published