dbcve.org
RustfsApplication

CVE-2026-24762

HIGH · 7.5 CVSS v3.1 Published 2026-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RustFS versions alpha.13 through alpha.81 log sensitive credential material (access keys, secret keys, session tokens) at INFO level, resulting in plaintext credentials being written to application logs accessible to log consumers.

MitigationUpgrade RustFS to version alpha.82 or later, audit existing logs for exposed credentials, and rotate any credentials that may have been logged.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RustfsApplication
Affected:= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify RustFS version
    Check the installed RustFS version in your project via Cargo.toml, Cargo.lock, or by running 'cargo list' if it's a dependency. Alternatively, check the binary or library version if RustFS is packaged separately.
    Affected if Version is alpha.13, alpha.14, alpha.15, alpha.16, alpha.17, alpha.18, alpha.19, alpha.20, alpha.21, alpha.22, alpha.23, alpha.24, alpha.25, alpha.26, alpha.27, alpha.28, alpha.29, alpha.30, alpha.31, alpha.32, alpha.33, alpha.34, alpha.35, alpha.36, alpha.37, alpha.38, alpha.39, alpha.40, alpha.41,
  2. Confirm logging is enabled
    Verify that your application or the RustFS library has logging configured at INFO level or higher (INFO, WARN, ERROR, or TRACE). Check your logging configuration files, environment variables (such as RUST_LOG), or code initialization that sets log levels.
    Affected if Logging is enabled at INFO level or higher and the vulnerable RustFS version is in use
  3. Check if credentials are configured
    Inspect your application configuration, environment variables, or code where RustFS is initialized to determine if access keys, secret keys, or session tokens are being passed to RustFS for authentication.
    Affected if Credentials (access keys, secret keys, or session tokens) are configured for use with RustFS
  4. Inspect logs for exposed credentials
    Search your application log files or log aggregation system for any plaintext instances of your access keys, secret keys, or session tokens that may have been logged by RustFS operations.
    Affected if Plaintext credentials appear in logs and the vulnerable version is deployed

Your environment is affected if RustFS version alpha.13 through alpha.81 is installed, logging is enabled at INFO level or higher, and credentials are configured for RustFS, resulting in potential credential exposure in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade RustFS to version alpha.82 or later, audit existing logs for exposed credentials, and rotate any credentials that may have been logged.

Recommended fix High confidence

alpha.82

  1. Identify the current RustFS version in use (check Cargo.toml or dependency lock file)
  2. Update RustFS dependency to version alpha.82 in Cargo.toml or equivalent dependency management file
  3. Run cargo update or equivalent to fetch the new version
  4. Rebuild the project to incorporate the patched version
  5. Verify the version upgrade was successful by checking the installed RustFS version
  6. Review application logs to confirm credentials are no longer being logged at INFO level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rustfs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24762 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24762 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data