{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/backup-restore-operator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "9.0.0"
            },
            {
              "fixed": "9.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/backup-restore-operator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "8.0.0"
            },
            {
              "fixed": "8.1.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/backup-restore-operator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7.0.0"
            },
            {
              "fixed": "7.0.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/rancher/backup-restore-operator"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "6.0.0"
            },
            {
              "fixed": "6.0.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-62879"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-532"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-03T16:44:18Z",
    "nvd_published_at": "2026-03-04T16:16:25Z",
    "severity": "MODERATE"
  },
  "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\u0027s logs.\n\nSpecifically, the S3 `accessKey` and `secretKey` are exposed in the pod\u0027s 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\u0026CK - 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/).",
  "id": "GHSA-wj3p-5h3x-c74q",
  "modified": "2026-03-04T18:38:37Z",
  "published": "2026-03-03T16:44:18Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Rancher Backup Operator pod\u0027s logs leak S3 tokens"
}