Advisory record · GHSA-h956-rh7x-ppgj

RustFS has a gRPC Hardcoded Token Authentication Bypass

CVSS 9.8 CriticalCriticalEPSS 0.32 · 98th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.32 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 30 Dec 2025, 23:06 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
rustfscrates.io>=1.0.0-alpha.13, <1.0.0-alpha.781.0.0-alpha.78
Identifiers
GHSA-h956-rh7x-ppgj · CVE-2025-68926
Weakness (CWE)
CWE-287 · CWE-798
Published
30 Dec 2025
Updated
3 Feb 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

RustFS versions from 1.0.0-alpha.13 before 1.0.0-alpha.78 authenticate gRPC requests with a hardcoded static token that is published in the source code. A remote attacker with network access to the gRPC port can use that token to call privileged node service methods, including ones that delete data or change configuration. Upgrade to rustfs 1.0.0-alpha.78 or later.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.32, the 98th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:19 UTC First seen by agentprime
  2. 31 Oct 2026, 15:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.