Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2025-62879

MEDIUM

CVE-2025-62879 is a medium-severity (CVSS 6.8) CWE-532 vulnerability in github.com/rancher/backup-restore-operator. O3 Security confirms whether CVE-2025-62879 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Rancher Backup Operator pod's logs leak S3 tokens

Also known asGHSA-wj3p-5h3x-c74qGO-2026-4591
Published
Mar 4, 2026
Updated
Jul 31, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Blast Radius

4 pkgs affected
🐹github.com/rancher/backup-restore-operator🐹github.com/rancher/backup-restore-operator🐹github.com/rancher/backup-restore-operator🐹github.com/rancher/backup-restore-operator

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/rancher/backup-restore-operator9.0.0&&< 9.0.19.0.1
🐹Gogithub.com/rancher/backup-restore-operator8.0.0&&< 8.1.28.1.2
🐹Gogithub.com/rancher/backup-restore-operator7.0.0&&< 7.0.57.0.5
🐹Gogithub.com/rancher/backup-restore-operator6.0.0&&< 6.0.36.0.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/backup-restore-operator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/rancher/backup-restore-operator to 9.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-62879 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-62879 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-62879. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2025-62879 in your dependencies?

O3 detects CVE-2025-62879 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.