Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.8
Rancher Backup Operator exposes S3 credentials in logs
CVE-2025-62879
GHSA-wj3p-5h3x-c74q
Summary
The Rancher Backup Operator accidentally logs sensitive Amazon S3 credentials, making them visible to unauthorized users. This is a security risk because attackers could use these credentials to access your S3 storage. To fix this, update to a patched version of Rancher Backup Operator or refresh your Rancher app repository if an update is not immediately possible.
What to do
- Update github.com rancher to version 9.0.1.
- Update github.com rancher to version 8.1.2.
- Update github.com rancher to version 7.0.5.
- Update github.com rancher to version 6.0.3.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| github.com | rancher | > 9.0.0 , <= 9.0.1 | 9.0.1 |
| github.com | rancher | > 8.0.0 , <= 8.1.2 | 8.1.2 |
| github.com | rancher | > 7.0.0 , <= 7.0.5 | 7.0.5 |
| github.com | rancher | > 6.0.0 , <= 6.0.3 | 6.0.3 |
| suse | rancher_backup_and_restore_operator | > 6.0.0 , <= 6.0.3 | – |
| suse | rancher_backup_and_restore_operator | > 7.0.0 , <= 7.0.5 | – |
| suse | rancher_backup_and_restore_operator | > 8.0.0 , <= 8.1.2 | – |
| suse | rancher_backup_and_restore_operator | > 9.0.0 , <= 9.0.1 | – |
Original title
Rancher Backup Operator pod's logs leak S3 tokens
Original description
### 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 - Technique - Log Enumeration](https://attack.mitre.org/techniques/T1654/).
### Patches
This vulnerability is addressed by applying redaction to sensitive information that was leaking.
Patched versions of Rancher Backup Operator include: `108.0.1+up9.0.1`, `107.1.2+up8.1.2`, `106.0.6+up7.0.5`, and `105.0.6+up6.0.3`.
### Workarounds
Users are advised to rotate both S3 `accessKey` and `secretKey` once they have upgraded to a fixed version, especially if logs are exported.
Users who cannot update Rancher are advised to refresh the Rancher app Repository, which should provide the ability to update just the Rancher Backup chart alone. This will patch the vulnerabilities without requiring Rancher to be updated. This will not work for Rancher clusters in an air-gap setup.
For air-gapped Rancher clusters, the Rancher version must be updated first, and then after you will find the patched version of the Rancher Backup chart to upgrade. You will also need to sync new images for the release to your image mirror.
Users who cannot update either Rancher or Rancher Backup should ensure that both debug and trace values are both false (default). Users should revert the values to the default until they can update to prevent potential leaks.
### References
If you have any questions or comments about this advisory:
- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
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 - Technique - Log Enumeration](https://attack.mitre.org/techniques/T1654/).
### Patches
This vulnerability is addressed by applying redaction to sensitive information that was leaking.
Patched versions of Rancher Backup Operator include: `108.0.1+up9.0.1`, `107.1.2+up8.1.2`, `106.0.6+up7.0.5`, and `105.0.6+up6.0.3`.
### Workarounds
Users are advised to rotate both S3 `accessKey` and `secretKey` once they have upgraded to a fixed version, especially if logs are exported.
Users who cannot update Rancher are advised to refresh the Rancher app Repository, which should provide the ability to update just the Rancher Backup chart alone. This will patch the vulnerabilities without requiring Rancher to be updated. This will not work for Rancher clusters in an air-gap setup.
For air-gapped Rancher clusters, the Rancher version must be updated first, and then after you will find the patched version of the Rancher Backup chart to upgrade. You will also need to sync new images for the release to your image mirror.
Users who cannot update either Rancher or Rancher Backup should ensure that both debug and trace values are both false (default). Users should revert the values to the default until they can update to prevent potential leaks.
### References
If you have any questions or comments about this advisory:
- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
nvd CVSS3.1
4.9
Vulnerability type
CWE-532
Insertion of Sensitive Information into Log File
Published: 3 Mar 2026 · Updated: 13 Mar 2026 · First seen: 6 Mar 2026