CVE-2025-68926
RustFS has a gRPC Hardcoded Token Authentication Bypass
In short
RustFS uses a hardcoded public token for authentication that anyone can see in the source code, allowing attackers on the network to pretend to be authorized users and delete data or change system settings.
Technical detail
RustFS prior to v1.0.0-alpha.78 implements gRPC authentication via a static, hardcoded token `"rustfs rpc"` exposed in the public repository, non-configurable and without rotation mechanisms. Any network-adjacent attacker can authenticate and execute privileged operations including data destruction and cluster configuration changes (CWE-287: Improper Authentication, CWE-798: Hardcoded Credentials).
Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Affected products
rustfs · rustfspublic PoCs found — 3
githubgithub.com/Chocapikk/CVE-2025-68926★ 10githubgithub.com/Arcueld/CVE-2025-68926★ 1githubgithub.com/materaj2/CVE-2025-68926-repo★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Want to know if your infrastructure is exposed to this?
Talk to TrueHacking →