RustFS Path Traversal Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-68705: 7.26% estimated exploitation activity in the next 30 days; percentile 94.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

RustFS Path Traversal Vulnerability Vulnerability Details - CVE ID: - Severity: Critical (CVSS estimated 9.9) - Impact: Arbitrary File Read/Write - Component: /rustfs/rpc/readfilestream endpoint - Root Cause: Insufficient path validation in crates/ecstore/src/disk/local.rs:1791 Vulnerable Code The code uses PathBuf::join() without: - Canonicalization - Path boundary validation - Protection against ../ sequences - Protection against absolute paths Proof of Concept Test Environment - Target: RustFS v0.0.5 (Docker container) - Endpoint: http://localhost:9000/rustfs/rpc/readfilestream - RPC Secret: rustfsadmin (from RUSTFSSECRETKEY) - Disk ID: /data/rustfs0 - Volume: .rustfs.sys Attack Scenario Exploit Parameters Required Authentication RPC requests require HMAC-SHA256 signature: Successful Exploits 1. Read /etc/passwd ✅ Request: Response: HTTP 200 OK Content Retrieved: Impact: Full user account enumeration --- 2. Read /etc/hosts ✅ Request: Response: HTTP 200 OK Content Retrieved:…

Published by the source

7 Jan 2026, 18:15 UTC

Last modified by the source

7 Jan 2026, 21:34 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pq29-69jg-9mxc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68705

Advisory: RustFS Path Traversal Vulnerability
IDs: CVE-2025-68705, GHSA-pq29-69jg-9mxc
Record: https://patchnext.com/advisories/cve-2025-68705 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rustfs 1.0.0-alpha.79. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rustfs: affected >= 1.0.0-alpha.13, <= 1.0.0-alpha.78; fixed in 1.0.0-alpha.79

## Suggested inspection (read-only)
- crates.io rustfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rustfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pq29-69jg-9mxc (GitHub-reviewed advisory GHSA-pq29-69jg-9mxc lists affected ranges: crates.io rustfs >=1.0.0-alpha.13 <=1.0.0-alpha.78)

Commands are suggestions: review each one before running it.