CVE-2024-58269 is a medium-severity (CVSS 4.3) CWE-532 vulnerability in github.com/rancher/rancher. A fix is available for github.com/rancher/rancher — see the affected versions and patch details below.
Rancher exposes sensitive information through audit logs
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-58269.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-58269 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/rancher/rancherReal-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
Impact
Note: The exploitation of this issue requires that the malicious user have access to Rancher’s audit log storage.
A vulnerability has been identified in Rancher Manager, where sensitive information, including secret data, cluster import URLs, and registration tokens, is exposed to any entity with access to Rancher audit logs. This happens in two different ways:
- Secret Annotation Leakage: When creating Kubernetes Secrets using the
stringDatafield, the cleartext value is embedded in thekubectl.kubernetes.io/last-applied-configurationannotation. This annotation is included in Rancher audit logs within both the request and response bodies, exposing secret material that should be redacted. - Cluster Registration Token Leakage: During the import or creation of downstream clusters (Custom, Imported, or Harvester), Rancher audit logs record full cluster registration manifests and tokens, including:
a. Non-expiring import URLs such as
/v3/import/<token>_c-m-xxxx.yaml. b. Fullkubectl applyandcurlcommands containing registration tokens and CA checksums. c. Token values associated with cluster registration resources (clusterRegistrationToken). d. These tokens are valid until explicitly revoked and can be used to re-register nodes, granting unauthorized cluster access.
An attacker or internal user who gains access to these logs could:
- Recover plaintext secret values from annotations.
- Use cluster registration tokens or import URLs to re-enroll agents or compromise downstream clusters.
- Access clusters that rely on these tokens for authentication, enabling lateral movement.
Please consult the associated MITRE ATT&CK - Technique - Log Enumeration for further information about this category of attack.
Patches
This vulnerability is addressed by applying redaction to sensitive information that was leaking.
Patched versions of Rancher include release v2.12.3.
Workarounds
If the deployment can't be upgraded to a fixed version, users are encouraged to create AuditPolicies to redact and filter some of those requests as described in our documentation.
The following AuditPolicy can be applied to redact the secrets:
apiVersion: auditlog.cattle.io/v1
kind: AuditPolicy
metadata:
name: redactions
spec:
enabled: true
additionalRedactions:
- headers:
- "Referer"
- paths:
- "$..metadata.annotations['kubectl.kubernetes.io/last-applied-configuration']"
Also consider granting access to Rancher's logs only for trusted users.
References
If you have any questions or comments about this advisory:
- Reach out to the SUSE Rancher Security team for security related inquiries.
- Open an issue in the Rancher repository.
- Verify with our support matrix and product support lifecycle.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/rancher/rancher | all versions | 0.0.0-20251013203444-50dc516a19eago get github.com/rancher/rancher@v0.0.0-20251013203444-50dc516a19ea |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rancher/rancher, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rancher/rancher to 0.0.0-20251013203444-50dc516a19ea or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-58269 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-58269 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-58269. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-58269 in your dependencies?
O3 Security finds CVE-2024-58269 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.