RustFS has a gRPC Hardcoded Token Authentication Bypass

Exploitation

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

CVSS

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

EPSS

• CVE-2025-68926: 31.85% estimated exploitation activity in the next 30 days; percentile 98.30 (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.

Vulnerability Overview Description RustFS implements gRPC authentication using a hardcoded static token "rustfs rpc" that is: 1. Publicly exposed in the source code repository 2. Hardcoded on both client and server sides 3. Non-configurable with no mechanism for token rotation 4. 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. CVSS 3.1 Score Score: 9.8 (Critical) Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - Attack Vector (AV): Network - Exploitable remotely - Attack Complexity (AC): Low - No special conditions required - Privileges Required (PR): None - No authentication needed (bypassed) - User Interaction (UI): None - Fully automated exploitation - Scope (S): Unchanged - Impact contained to vulnerable component - Confidentiality (C): High - Complete data…

Published by the source

30 Dec 2025, 23:06 UTC

Last modified by the source

7 Jan 2026, 15:22 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h956-rh7x-ppgj

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

# Patch Next advisory brief: CVE-2025-68926

Advisory: RustFS has a gRPC Hardcoded Token Authentication Bypass
IDs: CVE-2025-68926, GHSA-h956-rh7x-ppgj
Record: https://patchnext.com/advisories/cve-2025-68926 (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: Critical (CVSS 9.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.78. 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.77; fixed in 1.0.0-alpha.78

## 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-h956-rh7x-ppgj (GitHub-reviewed advisory GHSA-h956-rh7x-ppgj lists affected ranges: crates.io rustfs >=1.0.0-alpha.13 <=1.0.0-alpha.77)

Commands are suggestions: review each one before running it.