CVE-2025-68926

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 7.5%, top 8% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 29%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
9.8
EG Score
9.8(medium)
EPSS
98.0%
KEV
Not listed

Published

December 30, 2025

Last Modified

January 16, 2026

Advisory Details (1)

Auto-updated Jun 13, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

gRPC Hardcoded Token Authentication Bypass - Reproduction Report · Advisory · rustfs/rustfs · GitHub

https://github.com/rustfs/rustfs/security/advisories/GHSA-h956-rh7x-ppgj

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
rustfs—1.0.0-alpha.78—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 17:02 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 07:02 UTCOSV refresh
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 53 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-23 21:32 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-22 14:25 UTCEPSS rescore
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 14:56 UTCEPSS rescore
  16. 2026-06-21 01:59 UTCEPSS rescore
  17. 2026-06-21 01:59 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-17 18:14 UTCOSV refresh
  21. 2026-06-17 17:53 UTCEPSS rescore
  22. 2026-06-16 17:52 UTCEPSS rescore
  23. 2026-06-15 17:48 UTCEPSS rescore
  24. 2026-06-14 23:18 UTCEPSS rescore
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-13 23:00 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-11 14:00 UTCEPSS rescore
  30. 2026-06-10 22:18 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-08 14:17 UTCEPSS rescore
  33. 2026-06-08 14:17 UTCEPSS rescore
  34. 2026-06-07 15:24 UTCEPSS rescore
  35. 2026-06-07 15:24 UTCEPSS rescore
  36. 2026-06-06 13:47 UTCEPSS rescore
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-05 22:47 UTCEPSS rescore
  39. 2026-06-05 22:46 UTCEPSS rescore
  40. 2026-06-05 06:10 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-04 13:12 UTCEPSS rescore
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-02 20:13 UTCEPSS rescore
  45. 2026-06-01 13:51 UTCEPSS rescore
  46. 2026-06-01 13:51 UTCEPSS rescore
  47. 2026-05-31 22:30 UTCEPSS rescore
  48. 2026-05-31 22:30 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-31 00:16 UTCEPSS rescore
  51. 2026-05-29 16:51 UTCEG score recompute
  52. 2026-05-29 13:44 UTCEPSS rescore
  53. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCChocapikk/CVE-2025-68926
    First seen Jan 4, 2026

    CVE-2025-68926 - RustFS Hardcoded gRPC Authentication Token Exploit

    Open source ↗

Frequently asked(5)

What is CVE-2025-68926?
CVE-2025-68926 is a critical vulnerability published on December 30, 2025. 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…
When was CVE-2025-68926 disclosed?
CVE-2025-68926 was first published in the National Vulnerability Database on December 30, 2025, with the most recent update on January 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-68926 actively exploited?
CVE-2025-68926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-68926?
CVE-2025-68926 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-68926?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-68926, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-68926

Explore →

Is Your Infrastructure Affected by CVE-2025-68926?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs