dbcve.org
RustfsApplication

CVE-2025-68926

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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. In versions prior to 1.0.0-alpha.78, RustFS implements gRPC authentication using a hardcoded static token `"rustfs rpc"` that is publicly exposed in the source code repository, hardcoded on both client and server sides, non-configurable with no mechanism for token rotation, and universally valid across all RustFS deployments. Any attacker with network access to the gRPC port can authenticate using this publicly known token and execute privileged operations including data destruction, policy manipulation, and cluster configuration changes. Version 1.0.0-alpha.78 contains a fix for the issue.

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 distributed object storage uses a hardcoded static token 'rustfs rpc' embedded in both client and server code, visible in the public repository. This token is non-configurable, cannot be rotated, and is valid across all deployments. Attackers with network access to the gRPC port can authenticate using this known token to execute privileged operations including data destruction, policy changes, and cluster configuration modifications.

MitigationUpgrade to RustFS version 1.0.0-alpha.78 or later which implements proper configurable authentication. As an interim measure, restrict network access to the gRPC port to trusted sources only.

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
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 checks

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

  1. Identify RustFS installation and version
    Run 'rustfs --version' or check the installed package version using your system's package manager (e.g., 'dpkg -l rustfs', 'rpm -qi rustfs', or check the binary metadata)
    Affected if The installed version is 1.0.0-alpha.77 or earlier, or the version cannot be determined but is known to be from the 1.0.0 release line prior to alpha.78
  2. Locate the RustFS binary and configuration files
    Find the RustFS binary location using 'which rustfs' or 'where rustfs', then check the installation directory for configuration files such as config.yaml, config.toml, or any .json configuration files
    Affected if The binary exists and configuration files are present in the installation directory
  3. Determine if gRPC service is enabled and exposed
    Inspect the RustFS configuration files for gRPC-related settings (look for 'grpc', 'rpc', 'port', 'listen' keywords) and check if the gRPC port is listening using 'netstat -an | grep <grpc-port>' or 'ss -an | grep <grpc-port>'
    Affected if gRPC is enabled and the port is listening on a network interface accessible to attackers
  4. Check for presence of hardcoded authentication token
    Examine the RustFS binary or configuration for the literal string 'rustfs rpc' using 'strings <binary_path> | grep -i rustfs' or search configuration files with 'grep -r "rustfs rpc" <config_dir>'
    Affected if The hardcoded token 'rustfs rpc' is found in the binary or configuration files, indicating the vulnerable authentication method is in use

You are affected if RustFS version is prior to 1.0.0-alpha.78, gRPC is exposed on a network, and the hardcoded token 'rustfs rpc' is present in the deployment.

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 to RustFS version 1.0.0-alpha.78 or later which implements proper configurable authentication. As an interim measure, restrict network access to the gRPC port to trusted sources only.

Recommended fix High confidence

1.0.0-alpha.78

  1. 1. Identify all RustFS deployments running versions prior to 1.0.0-alpha.78
  2. 2. Review current client configurations that may rely on the hardcoded token
  3. 3. Create a backup of the current configuration and data
  4. 4. Upgrade RustFS to version 1.0.0-alpha.78 or later
  5. 5. Reconfigure clients to use the new proper authentication mechanism
  6. 6. Verify the hardcoded token no longer provides access
  7. 7. Test privileged operations work with the new authentication
Caveat Upgrade requires migrating from hardcoded token to proper authentication; ensure client configurations are updated

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

Fix this in Rustfs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-68926 — 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-2025-68926 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