Rancher Backup Operator pod's logs leak S3 tokens

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2025-62879: 0.38% estimated exploitation activity in the next 30 days; percentile 31.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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…

Published by the source

3 Mar 2026, 16:44 UTC

Last modified by the source

4 Mar 2026, 18:38 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wj3p-5h3x-c74q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-62879

Advisory: Rancher Backup Operator pod's logs leak S3 tokens
IDs: CVE-2025-62879, GHSA-wj3p-5h3x-c74q
Record: https://patchnext.com/advisories/cve-2025-62879 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/rancher/backup-restore-operator 9.0.1, 8.1.2, 7.0.5, 6.0.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/rancher/backup-restore-operator: affected >= 9.0.0, < 9.0.1; >= 8.0.0, < 8.1.2; >= 7.0.0, < 7.0.5; >= 6.0.0, < 6.0.3; fixed in 6.0.3, 8.1.2, 9.0.1, 7.0.5

## Suggested inspection (read-only)
- Go github.com/rancher/backup-restore-operator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/rancher/backup-restore-operator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-wj3p-5h3x-c74q (GitHub-reviewed advisory GHSA-wj3p-5h3x-c74q lists affected ranges: Go github.com/rancher/backup-restore-operator >=9.0.0 =8.0.0 =7.0.0 =6.0.0 <6.0.3)

Commands are suggestions: review each one before running it.