Skip to content
Fencer Vulns
critical 9.8

CVE-2025-68926 in the critical feed json

RustFS has a gRPC Hardcoded Token Authentication Bypass

published 2025-12-30 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-205801 , GHSA-h956-rh7x-ppgj

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
31.9%
EPSS 31.9% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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.

Patch / fix

  • crates.io rustfs 1.0.0-alpha.78
  • rustfs rustfs 1.0.0-alpha.78

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
10 mo ago

Exploit prediction

31.85% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rustfs/rustfs/security/advisories/GHSA-h956-rh7x-ppgj referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
crates.io rustfs
>=1.0.0-alpha.13, <1.0.0-alpha.78
1.0.0-alpha.78

Affected products

  • rustfs rustfs

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials
  • CWE-287 Improper Authentication

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.