RustFS up to 1.0.0-alpha.76 gRPC Authentication hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in RustFS up to 1.0.0-alpha.76. This affects an unknown function of the component gRPC Authentication. This manipulation causes hard-coded credentials. This vulnerability is handled as CVE-2025-68926. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in RustFS up to 1.0.0-alpha.76 and classified as critical. Affected by this vulnerability is some unknown functionality of the component gRPC Authentication. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-68926 since 12/25/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
Upgrading to version 1.0.0-alpha.77 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-205801). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.0.0-alpha.0
- 1.0.0-alpha.1
- 1.0.0-alpha.2
- 1.0.0-alpha.3
- 1.0.0-alpha.4
- 1.0.0-alpha.5
- 1.0.0-alpha.6
- 1.0.0-alpha.7
- 1.0.0-alpha.8
- 1.0.0-alpha.9
- 1.0.0-alpha.10
- 1.0.0-alpha.11
- 1.0.0-alpha.12
- 1.0.0-alpha.13
- 1.0.0-alpha.14
- 1.0.0-alpha.15
- 1.0.0-alpha.16
- 1.0.0-alpha.17
- 1.0.0-alpha.18
- 1.0.0-alpha.19
- 1.0.0-alpha.20
- 1.0.0-alpha.21
- 1.0.0-alpha.22
- 1.0.0-alpha.23
- 1.0.0-alpha.24
- 1.0.0-alpha.25
- 1.0.0-alpha.26
- 1.0.0-alpha.27
- 1.0.0-alpha.28
- 1.0.0-alpha.29
- 1.0.0-alpha.30
- 1.0.0-alpha.31
- 1.0.0-alpha.32
- 1.0.0-alpha.33
- 1.0.0-alpha.34
- 1.0.0-alpha.35
- 1.0.0-alpha.36
- 1.0.0-alpha.37
- 1.0.0-alpha.38
- 1.0.0-alpha.39
- 1.0.0-alpha.40
- 1.0.0-alpha.41
- 1.0.0-alpha.42
- 1.0.0-alpha.43
- 1.0.0-alpha.44
- 1.0.0-alpha.45
- 1.0.0-alpha.46
- 1.0.0-alpha.47
- 1.0.0-alpha.48
- 1.0.0-alpha.49
- 1.0.0-alpha.50
- 1.0.0-alpha.51
- 1.0.0-alpha.52
- 1.0.0-alpha.53
- 1.0.0-alpha.54
- 1.0.0-alpha.55
- 1.0.0-alpha.56
- 1.0.0-alpha.57
- 1.0.0-alpha.58
- 1.0.0-alpha.59
- 1.0.0-alpha.60
- 1.0.0-alpha.61
- 1.0.0-alpha.62
- 1.0.0-alpha.63
- 1.0.0-alpha.64
- 1.0.0-alpha.65
- 1.0.0-alpha.66
- 1.0.0-alpha.67
- 1.0.0-alpha.68
- 1.0.0-alpha.69
- 1.0.0-alpha.70
- 1.0.0-alpha.71
- 1.0.0-alpha.72
- 1.0.0-alpha.73
- 1.0.0-alpha.74
- 1.0.0-alpha.75
- 1.0.0-alpha.76
Website
- Product: https://github.com/rustfs/rustfs/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: RustFS 1.0.0-alpha.77
Timeline
12/25/2025 CVE reserved12/30/2025 Advisory disclosed
12/30/2025 VulDB entry created
01/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-h956-rh7x-ppgj
Status: Confirmed
CVE: CVE-2025-68926 (🔒)
GCVE (CVE): GCVE-0-2025-68926
GCVE (VulDB): GCVE-100-339061
EUVD: 🔒
Entry
Created: 12/30/2025 18:33Updated: 01/05/2026 16:31
Changes: 12/30/2025 18:33 (64), 12/30/2025 19:59 (1), 01/05/2026 16:31 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.