CVE-2025-62879GO-2026-4591GHSA-WJ3P-5H3X-C74Q
Rancher Backup Operator pod's logs leak S3 tokens
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 9.0.1, 8.1.2, 7.0.5, 6.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- github.com/rancher/backup-restore-operator
From 9.0.0 · fixed in 9.0.1; From 8.0.0 · fixed in 8.1.2; From 7.0.0 · fixed in 7.0.5; From 6.0.0 · fixed in 6.0.3
- github.com/rancher/backup-restore-operatorGo
All versions
- github.com/rancher/backup-restore-operatorGo
From 9.0.0 · fixed in 9.0.1
- github.com/rancher/backup-restore-operatorGo
From 8.0.0 · fixed in 8.1.2
- github.com/rancher/backup-restore-operatorGo
From 7.0.0 · fixed in 7.0.5
- github.com/rancher/backup-restore-operatorGo
From 6.0.0 · fixed in 6.0.3