cve.bz

CVE-2025-68926 rustfs rustfs: Improper Authentication

9.8 criticalExploit referenceEPSS 32%Fix available

Critical (9.8) in rustfs rustfs. EPSS 32% estimated probability of exploitation activity in the next 30 days. Fixed in rustfs 1.0.0-alpha.78.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
32% (unchanged from 32% a week ago; 32% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2025-12-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-287 Improper Authentication
CWE-798 Use of Hard-coded Credentials
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68926 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68926?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68926?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68926 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
rustfs:rustfs1.0.0:alpha1
rustfs:rustfs1.0.0:alpha10
rustfs:rustfs1.0.0:alpha11
rustfs:rustfs1.0.0:alpha12
rustfs:rustfs1.0.0:alpha13
rustfs:rustfs1.0.0:alpha14
rustfs:rustfs1.0.0:alpha15
rustfs:rustfs1.0.0:alpha16
rustfs:rustfs1.0.0:alpha17
rustfs:rustfs1.0.0:alpha18
rustfs:rustfs1.0.0:alpha19
rustfs:rustfs1.0.0:alpha2
rustfs:rustfs1.0.0:alpha20
rustfs:rustfs1.0.0:alpha21
rustfs:rustfs1.0.0:alpha22
rustfs:rustfs1.0.0:alpha23
rustfs:rustfs1.0.0:alpha24
rustfs:rustfs1.0.0:alpha25
rustfs:rustfs1.0.0:alpha26
rustfs:rustfs1.0.0:alpha27
rustfs:rustfs1.0.0:alpha28
rustfs:rustfs1.0.0:alpha29
rustfs:rustfs1.0.0:alpha3
rustfs:rustfs1.0.0:alpha30
rustfs:rustfs1.0.0:alpha31
rustfs:rustfs1.0.0:alpha32
rustfs:rustfs1.0.0:alpha33
rustfs:rustfs1.0.0:alpha34
rustfs:rustfs1.0.0:alpha35
rustfs:rustfs1.0.0:alpha36
rustfs:rustfs1.0.0:alpha37
rustfs:rustfs1.0.0:alpha38
rustfs:rustfs1.0.0:alpha39
rustfs:rustfs1.0.0:alpha4
rustfs:rustfs1.0.0:alpha40
rustfs:rustfs1.0.0:alpha41
rustfs:rustfs1.0.0:alpha42
rustfs:rustfs1.0.0:alpha43
rustfs:rustfs1.0.0:alpha44
rustfs:rustfs1.0.0:alpha45
rustfs:rustfs1.0.0:alpha46
rustfs:rustfs1.0.0:alpha47
rustfs:rustfs1.0.0:alpha48
rustfs:rustfs1.0.0:alpha49
rustfs:rustfs1.0.0:alpha5
rustfs:rustfs1.0.0:alpha50
rustfs:rustfs1.0.0:alpha51
rustfs:rustfs1.0.0:alpha52
rustfs:rustfs1.0.0:alpha53
rustfs:rustfs1.0.0:alpha54
rustfs:rustfs1.0.0:alpha55
rustfs:rustfs1.0.0:alpha56
rustfs:rustfs1.0.0:alpha57
rustfs:rustfs1.0.0:alpha58
rustfs:rustfs1.0.0:alpha59
rustfs:rustfs1.0.0:alpha6
rustfs:rustfs1.0.0:alpha60
rustfs:rustfs1.0.0:alpha61
rustfs:rustfs1.0.0:alpha62
rustfs:rustfs1.0.0:alpha63
rustfs:rustfs1.0.0:alpha64
rustfs:rustfs1.0.0:alpha65
rustfs:rustfs1.0.0:alpha66
rustfs:rustfs1.0.0:alpha67
rustfs:rustfs1.0.0:alpha68
rustfs:rustfs1.0.0:alpha69
rustfs:rustfs1.0.0:alpha7
rustfs:rustfs1.0.0:alpha70
rustfs:rustfs1.0.0:alpha71
rustfs:rustfs1.0.0:alpha72
rustfs:rustfs1.0.0:alpha73
rustfs:rustfs1.0.0:alpha74
rustfs:rustfs1.0.0:alpha75
rustfs:rustfs1.0.0:alpha76
rustfs:rustfs1.0.0:alpha77
rustfs:rustfs1.0.0:alpha8
rustfs:rustfs1.0.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-h956-rh7x-ppgjcrates.iorustfs>=1.0.0-alpha.13 <1.0.0-alpha.781.0.0-alpha.78

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-287.

References

Check your stackJSON