# CVE-2024-58269: Rancher exposes sensitive information through audit logs

> Attackers with audit log access can view sensitive secrets, cluster URLs, and registration tokens in Rancher Manager.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-mw39-9qc2-f7mg, GO-2025-4074

## What is CVE-2024-58269?

CVE-2024-58269 is a medium-severity vulnerability in SUSE rancher, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-58269?

3 open source packages ship an affected version, including github.com/rancher/rancher.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/rancher/rancher` | Go | All versions | 0.0.0-20251013203444-50dc516a19ea |
| `github.com/rancher/rancher` | Go | All versions | 0.0.0-20251013203444-50dc516a19ea |
| `github.com/rancher/rancher` | Go | All versions | 0.0.0-20251013203444-50dc516a19ea |

## How do I fix CVE-2024-58269?

Upgrade github.com/rancher/rancher to 0.0.0-20251013203444-50dc516a19ea or later.

## Is CVE-2024-58269 being exploited?

There is no known exploitation of CVE-2024-58269 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58269 and fix it if it is affected.

What it is: CVE-2024-58269 is a medium-severity vulnerability in SUSE rancher, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58269 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20251013203444-50dc516a19ea
- github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20251013203444-50dc516a19ea
- github.com/rancher/rancher (Go): affected all versions; fixed in 0.0.0-20251013203444-50dc516a19ea

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58269/ (Markdown: https://insights.sbomify.com/CVE-2024-58269/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58269
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58269
- OSV: https://osv.dev/vulnerability/CVE-2024-58269

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58269/
Summaries are generated and may contain mistakes; the official description above is the record.