{"answers":{"affected":"2 open source packages ship an affected version, including rustfs. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68926 exists.","fix":"Upgrade rustfs to 1.0.0-alpha.78 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-68926 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68926 exists.\n\nAffected packages and fixed versions:\n- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.78\n- rustfs (crates.io): affected from 1.0.0-alpha.13; fixed in 1.0.0-alpha.78\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-68926/ (Markdown: https://insights.sbomify.com/CVE-2025-68926/index.md)","id":"CVE-2025-68926","markdown":"https://insights.sbomify.com/CVE-2025-68926/index.md","name":"CVE-2025-68926","record":{"aliases":["GHSA-h956-rh7x-ppgj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Distributed object storage","requires_auth":"none","summary":"Attackers can bypass gRPC authentication using a hardcoded token to execute privileged operations like data destruction and configuration changes in RustFS.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rustfs","vendor":"rustfs"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-287","name":"Improper Authentication"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":"2026-01-04","github_poc":3,"max_poc_stars":9,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-04T17:19:27Z","kind":"github_poc","ref":"https://github.com/Chocapikk/CVE-2025-68926","stars":9,"title":"CVE-2025-68926 - RustFS Hardcoded gRPC Authentication Token Exploit"},{"date":"2026-01-05T16:12:07Z","kind":"github_poc","ref":"https://github.com/Arcueld/CVE-2025-68926","stars":1,"title":"CVE-2025-68926 POC"},{"date":"2026-03-14T13:36:58Z","kind":"github_poc","ref":"https://github.com/materaj2/CVE-2025-68926-repo","stars":0,"title":"Script and node.proto for exploit CVE-2025-68926"}],"tier":"weaponised"},"has_fix":true,"headline":"RustFS has a gRPC Hardcoded Token Authentication Bypass","id":"CVE-2025-68926","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Improper Neutralization of HTML Tags in a Web Page in libredesk","id":"CVE-2025-68927"},"packages":[{"ecosystem":"crates.io","fixed":["1.0.0-alpha.78"],"introduced":["1.0.0-alpha.13"],"last_affected":[],"package":"rustfs","purl":null,"source":"GHSA-h956-rh7x-ppgj"},{"ecosystem":"crates.io","fixed":["1.0.0-alpha.78"],"introduced":["1.0.0-alpha.13"],"last_affected":[],"package":"rustfs","purl":"pkg:cargo/rustfs","source":"GHSA-h956-rh7x-ppgj"}],"prev":{"headline":"Jervis has a JWT Algorithm Confusion Vulnerability","id":"CVE-2025-68925"},"products":["rustfs"],"published":"2025-12-30","related":[{"cvss_score":9.1,"headline":"Rust has Critical Stored XSS in Preview Modal, leading to Administrative Account Takeover","id":"CVE-2026-27822","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":8.8,"headline":"RustFS Path Traversal Vulnerability","id":"CVE-2025-68705","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":8.3,"headline":"RustFS: Missing admin authorization on notification target endpoints allows unauthenticated configuration of event webhooks","id":"CVE-2026-40937","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.1,"headline":"RustFS's Missing Post Policy Validation leads to Arbitrary Object Write","id":"CVE-2026-27607","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":7.7,"headline":"RustFS sourceIp bypass via spoofed X-Forwarded-For/Real-IP headers","id":"CVE-2026-21862","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":6.9,"headline":"RustFS Logs Sensitive Credentials in Plaintext","id":"CVE-2026-24762","kev_date_added":null,"published":"2026-02-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["rustfs"]},"summary":"Attackers can bypass gRPC authentication using a hardcoded token to execute privileged operations like data destruction and configuration changes in RustFS.","url":"https://insights.sbomify.com/CVE-2025-68926/"}