# CVE-2025-68926: RustFS has a gRPC Hardcoded Token Authentication Bypass

> Attackers can bypass gRPC authentication using a hardcoded token to execute privileged operations like data destruction and configuration changes in RustFS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-h956-rh7x-ppgj

## What is CVE-2025-68926?

CVE-2025-68926 is a critical vulnerability in rustfs, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-68926?

2 open source packages ship an affected version, including rustfs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rustfs` | crates.io | From 1.0.0-alpha.13 | 1.0.0-alpha.78 |
| `rustfs` | crates.io | From 1.0.0-alpha.13 | 1.0.0-alpha.78 |

Products: Rustfs Rustfs.

## How do I fix CVE-2025-68926?

Upgrade rustfs to 1.0.0-alpha.78 or later.

## Is CVE-2025-68926 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68926 exists.

Public exploit code:

- CVE-2025-68926 - RustFS Hardcoded gRPC Authentication Token Exploit (github_poc): https://github.com/Chocapikk/CVE-2025-68926
- CVE-2025-68926 POC (github_poc): https://github.com/Arcueld/CVE-2025-68926
- Script and node.proto for exploit CVE-2025-68926 (github_poc): https://github.com/materaj2/CVE-2025-68926-repo

## Other vulnerabilities in rustfs

- [CVE-2026-27822](https://insights.sbomify.com/CVE-2026-27822/): Rust has Critical Stored XSS in Preview Modal, leading to Administrative Account Takeover (critical 9.1)
- [CVE-2025-68705](https://insights.sbomify.com/CVE-2025-68705/): RustFS Path Traversal Vulnerability (high 8.8)
- [CVE-2026-40937](https://insights.sbomify.com/CVE-2026-40937/): RustFS: Missing admin authorization on notification target endpoints allows unauthenticated configuration of event webhooks (high 8.3)
- [CVE-2026-27607](https://insights.sbomify.com/CVE-2026-27607/): RustFS's Missing Post Policy Validation leads to Arbitrary Object Write (high 8.1)
- [CVE-2026-21862](https://insights.sbomify.com/CVE-2026-21862/): RustFS sourceIp bypass via spoofed X-Forwarded-For/Real-IP headers (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68926 and fix it if it is affected.

What it is: CVE-2025-68926 is a critical vulnerability in rustfs, published on 30 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68926 exists.

Affected packages and fixed versions:
- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.78
- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.78

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68926/ (Markdown: https://insights.sbomify.com/CVE-2025-68926/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68926
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68926
- OSV: https://osv.dev/vulnerability/CVE-2025-68926

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68926/
Summaries are generated and may contain mistakes; the official description above is the record.