CVE-2026-45040
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 · uneditedRustFS is a distributed object storage system built in Rust. Prior to 1.0.0-beta.2, RustFS suffers from sensitive information leakage in log outputs. When the server is run with RUST_LOG=debug sensitive credentials including SessionToken (JWT), SecretAccessKey, and full JWT claims are printed in plaintext to the server logs. This vulnerability is fixed in 1.0.0-beta.2.
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 confidenceRustFS versions prior to 1.0.0-beta.2 expose sensitive credentials in plaintext when the server runs with RUST_LOG=debug. Specifically, SessionToken (JWT), SecretAccessKey, and full JWT claims are written to server logs, allowing unauthorized parties with log access to obtain these credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 checksWork through these to decide whether this CVE applies to you.
-
Identify RustFS versionRun 'rustfs --version' or check the installed package/version file to determine the currently running version of RustFSAffected if Version is prior to 1.0.0-beta.2 (e.g., 1.0.0-beta.1, 1.0.0-alpha.x, or any pre-1.0.0 release)
-
Check RUST_LOG environment variableRun 'echo $RUST_LOG' or inspect the environment variables set for the RustFS server processAffected if RUST_LOG is set to 'debug' or contains 'debug' level logging (e.g., RUST_LOG=debug, RUST_LOG=rustfs=debug)
-
Inspect server logs for sensitive dataExamine RustFS server log files (typically in /var/log/ or the configured log directory) and search for plaintext strings such as 'SessionToken', 'SecretAccessKey', or JWT token patterns (base64-encoded segments separated by dots)Affected if Log files contain plaintext SessionToken values, SecretAccessKey strings, or unredacted JWT tokens
-
Verify JWT claims exposureSearch logs for JSON-like structures containing claims fields (such as 'sub', 'exp', 'iat', 'iss') that appear alongside user authentication tokensAffected if Full JWT claims (including subject, expiration, issuer) are present in logs in plaintext form
Environment is affected if RustFS version is below 1.0.0-beta.2 AND the RUST_LOG environment variable enables debug-level logging, resulting in plaintext credentials appearing in server logs.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to RustFS version 1.0.0-beta.2 or later, which implements proper sanitization of sensitive data in log outputs. Until upgraded, avoid using RUST_LOG=debug in production environments.
1.0.0-beta.2
- Check the current version of RustFS being used in your deployment
- Upgrade RustFS to version 1.0.0-beta.2 or later
- After upgrading, verify that sensitive credentials (SessionToken, SecretAccessKey, JWT claims) are no longer logged when running with RUST_LOG=debug
- Ensure any existing logs from prior versions are reviewed and redacted if they may contain exposed credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45040 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45040 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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