Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Rancher Backup Operator pod's logs leak S3 tokens

CVSS 3.1 6.8 MEDIUMEUVD CVSS 3.1 6.8 CVSS 3.1 · [email protected] · Secondary 6.8 MEDIUMCVSS 3.1 · [email protected] · Primary 4.9 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/rancher/backup-restore-operator 9.0.1Fixed by github.com/rancher/backup-restore-operator 8.1.2Fixed by github.com/rancher/backup-restore-operator 7.0.5Fixed by github.com/rancher/backup-restore-operator 6.0.3osv · severity unknownKEV status unknown

cve-program · CVE-2025-62879

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-208270

Published

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.

Read the publisher's advisory

nvd · CVE-2025-62879

Published

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.

Read the publisher's advisory

osv · GHSA-wj3p-5h3x-c74q

Published

### 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/).

Read the publisher's advisory

osv · GO-2026-4591

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 10:01 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current