RustfsApplication
CVE-2025-68705
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. In versions 1.0.0-alpha.13 to 1.0.0-alpha.78, RustFS contains a path traversal vulnerability in the /rustfs/rpc/read_file_stream endpoint. This issue has been patched in version 1.0.0-alpha.79.
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 confidenceA path traversal vulnerability in the /rustfs/rpc/read_file_stream endpoint of RustFS versions 1.0.0-alpha.13 to 1.0.0-alpha.78 allows remote attackers to access arbitrary files on the storage system by manipulating file path parameters, potentially exposing sensitive data.
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
= 1.0.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify RustFS is installedIdentify whether RustFS is present in your environment by checking for running processes, services, or installed packages named 'rustfs' or 'RustFS'.Affected if RustFS is installed and running
-
Determine RustFS versionCheck the installed version of RustFS using package manager queries, service introspection, or configuration files that specify the version. Compare it against the affected range: 1.0.0-alpha.13 through 1.0.0-alpha.78.Affected if The installed version falls within 1.0.0-alpha.13 to 1.0.0-alpha.78 inclusive
-
Confirm endpoint exposureInspect your network configuration, API gateway settings, or firewall rules to determine if the /rustfs/rpc/read_file_stream HTTP endpoint is exposed and reachable.Affected if The /rustfs/rpc/read_file_stream endpoint is externally or internally accessible
You are affected if RustFS version 1.0.0-alpha.13 through 1.0.0-alpha.78 is installed and the /rustfs/rpc/read_file_stream endpoint is accessible.
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-alpha.79 or later which contains the patch. If immediate patching is not feasible, implement strict input validation and path sanitization on the read_file_stream endpoint to prevent directory traversal sequences.
1.0.0-alpha.79 or later
- Identify the currently deployed RustFS version using your deployment manifests or package manager
- If the version is between 1.0.0-alpha.13 and 1.0.0-alpha.78 (inclusive), plan an upgrade
- Upgrade RustFS to version 1.0.0-alpha.79 or later to obtain the patched version
- Verify the upgrade by checking that the /rustfs/rpc/read_file_stream endpoint no longer accepts path traversal sequences (e.g., ../)
- Deploy the upgraded version in a staging environment first to confirm functionality before production rollout
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rustfs
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68705 — 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-2025-68705 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