Vulnerabilities in pkg:golang/github.com/rancher/backup-restore-operator

PACKAGE
Advisory Identifier: GHSA-wj3p-5h3x-c74q
Advisory Summary

CVE-2025-62879 is a MODERATE (CVSS 6.8) rancher backup operator pod's logs vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting Github.com/rancher/backup restore operator libraries in the Go ecosystem. The issue involves rancher backup operator pod's logs leak s3 tokens. Remediation is available by upgrading affected packages to version 9.0.1, 8.1.2, 7.0.5, 6.0.3.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/rancher/backup-restore-operator

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/rancher/backup-restore-operator. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-wj3p-5h3x-c74q CVE-2025-62879 MODERATE Rancher Backup Operator pod's logs leak S3 tokens

CVE-2025-62879 at a Glance

CVE Identifier CVE-2025-62879
GHSA Identifier GHSA-wj3p-5h3x-c74q
Severity MODERATE
CVSS v3.1 Base Score 6.8
CWE Classification CWE-532: Insertion of Sensitive Information into Log File
Affected Product Github.com/rancher/backup restore operator
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-62879

To remediate this vulnerability, upgrade all affected Github.com/rancher/backup restore operator dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/rancher/backup-restore-operator fixed: 9.0.1
Upgrade github.com/rancher/backup-restore-operator to 9.0.1
github.com/rancher/backup-restore-operator fixed: 8.1.2
Upgrade github.com/rancher/backup-restore-operator to 8.1.2
github.com/rancher/backup-restore-operator fixed: 7.0.5
Upgrade github.com/rancher/backup-restore-operator to 7.0.5
github.com/rancher/backup-restore-operator fixed: 6.0.3
Upgrade github.com/rancher/backup-restore-operator to 6.0.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/rancher/backup-restore-operator

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-62879, inspect your project dependencies for Github.com/rancher/backup restore operator:

inspect dependencies for github.com/rancher/backup-restore-operator

Analyze the terminal output to locate any version of Github.com/rancher/backup restore operator in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 9.0.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In Github.com/rancher/backup restore operator, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2025-62879 Affected Github.com/rancher/backup restore operator Versions

4 component(s)
Fixed Versions:
9.0.18.1.27.0.56.0.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/rancher/backup-restore-operator
Go
≥ 9.0.0
< 9.0.1
9.0.1
github.com/rancher/backup-restore-operator
Go
≥ 8.0.0
< 8.1.2
8.1.2
github.com/rancher/backup-restore-operator
Go
≥ 7.0.0
< 7.0.5
7.0.5
github.com/rancher/backup-restore-operator
Go
≥ 6.0.0
< 6.0.3
6.0.3

References

Frequently Asked Questions

What is CVE-2025-62879?
CVE-2025-62879 is a security vulnerability in Github.com/rancher/backup restore operator involving Rancher Backup Operator pod's logs leak S3 tokens under CWE-532: Insertion of Sensitive Information into Log File.
Which Github.com/rancher/backup restore operator versions are affected?
Affected versions include releases prior to 9.0.1, 8.1.2, 7.0.5, 6.0.3 across affected packages: github.com/rancher/backup-restore-operator.
What version fixes CVE-2025-62879?
Upgrading to 9.0.1, 8.1.2, 7.0.5, 6.0.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/rancher/backup-restore-operator affected?
Yes, github.com/rancher/backup-restore-operator is affected in releases prior to 9.0.1, 8.1.2, 7.0.5, 6.0.3. Upgrade your dependency to 9.0.1, 8.1.2, 7.0.5, 6.0.3 or later.
What is the CVSS score of CVE-2025-62879?
CVE-2025-62879 has a CVSS v3.1 base score of 6.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2025-62879?
CVE-2025-62879 is classified under CWE-532: Insertion of Sensitive Information into Log File (The product writes sensitive information to a log file.).
How can I check Go dependencies for CVE-2025-62879?
Run the dependency tree command: 'inspect dependencies for github.com/rancher/backup-restore-operator'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wj3p-5h3x-c74q",
  "modified" : "2026-03-04T18:38:37Z",
  "published" : "2026-03-03T16:44:18Z",
  "aliases" : [ "CVE-2025-62879" ],
  "summary" : "Rancher Backup Operator pod's logs leak S3 tokens",
  "details" : "### Impact\nA 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.\n\nSpecifically, the S3 `accessKey` and `secretKey` are exposed in the pod's logs under the following logging level conditions:\n\n| Variable Exposed | Logging Level Condition | \n------------------ | ------------------------- |\n| accessKey            | `trace: false` (default), and `debug: false` (default) |\n| secretKey             | `trace: true` or `debug: true`|\n\n**Note:** The S3 `accessKey` is exposed in the logs without requiring any supplementary configuration.\n\nFor further information on this attack category, please consult the associated [MITRE ATT&CK - Technique - Log Enumeration](https://attack.mitre.org/techniques/T1654/).\n\n### Patches\nThis vulnerability is addressed by applying redaction to sensitive information that was leaking.\n\nPatched 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`.\n\n### Workarounds\nUsers are advised to rotate both S3 `accessKey` and `secretKey` once they have upgraded to a fixed version, especially if logs are exported.\n\nUsers 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.\n\nFor 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.\n\nUsers 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.\n\n### References\nIf you have any questions or comments about this advisory:\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.\n- 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/).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/backup-restore-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "9.0.0"
      }, {
        "fixed" : "9.0.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/backup-restore-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "8.0.0"
      }, {
        "fixed" : "8.1.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/backup-restore-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "7.0.0"
      }, {
        "fixed" : "7.0.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/rancher/backup-restore-operator"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0"
      }, {
        "fixed" : "6.0.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rancher/backup-restore-operator/security/advisories/GHSA-wj3p-5h3x-c74q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62879"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-62879"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rancher/backup-restore-operator"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-532" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-03T16:44:18Z",
    "nvd_published_at" : "2026-03-04T16:16:25Z"
  }
}