# CVE-2026-24762: RustFS Logs Sensitive Credentials in Plaintext

> RustFS logs sensitive credentials in plaintext, allowing attackers with log access to steal keys and compromise accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-r54g-49rx-98cr

## What is CVE-2026-24762?

CVE-2026-24762 is a medium-severity vulnerability in rustfs, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RustFS is a distributed object storage system built in Rust. From versions alpha.13 to alpha.81, RustFS logs sensitive credential material (access key, secret key, session token) to application logs at INFO level. This results in credentials being recorded in plaintext in log output, which may be accessible to internal or external log consumers and could lead to compromise of sensitive credentials. This issue has been patched in version alpha.82.

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

## Which versions are affected by CVE-2026-24762?

2 open source packages ship an affected version, including rustfs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rustfs` | crates.io | From 1.0.0-alpha.13 | 1.0.0-alpha.82 |
| `rustfs` | crates.io | From 1.0.0-alpha.13 | 1.0.0-alpha.82 |

Products: Rustfs Rustfs.

## How do I fix CVE-2026-24762?

Upgrade rustfs to 1.0.0-alpha.82 or later.

## Is CVE-2026-24762 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24762 exists.

## Other vulnerabilities in rustfs

- [CVE-2025-68926](https://insights.sbomify.com/CVE-2025-68926/): RustFS has a gRPC Hardcoded Token Authentication Bypass (critical 9.8)
- [CVE-2026-27822](https://insights.sbomify.com/CVE-2026-27822/): Rust has Critical Stored XSS in Preview Modal, leading to Administrative Account Takeover (critical 9.1)
- [CVE-2025-68705](https://insights.sbomify.com/CVE-2025-68705/): RustFS Path Traversal Vulnerability (high 8.8)
- [CVE-2026-40937](https://insights.sbomify.com/CVE-2026-40937/): RustFS: Missing admin authorization on notification target endpoints allows unauthenticated configuration of event webhooks (high 8.3)
- [CVE-2026-27607](https://insights.sbomify.com/CVE-2026-27607/): RustFS's Missing Post Policy Validation leads to Arbitrary Object Write (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24762 and fix it if it is affected.

What it is: CVE-2026-24762 is a medium-severity vulnerability in rustfs, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24762 exists.

Affected packages and fixed versions:
- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.82
- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.82

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-2026-24762/ (Markdown: https://insights.sbomify.com/CVE-2026-24762/index.md)
```

## Sources

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

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