GHSA-2v6v-25fm-p4fg is a critical-severity (CVSS 9.8) Missing Authentication vulnerability in github.com/seaweedfs/seaweedfs. A fix is available for github.com/seaweedfs/seaweedfs — see the affected versions and patch details below.
SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2v6v-25fm-p4fg.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2v6v-25fm-p4fg plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/seaweedfs/seaweedfsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The filer registered the IAM gRPC service (SeaweedIdentityAccessManagement) with no authentication. Any client able to reach the filer gRPC port could invoke IAM RPCs — CreateUser, CreateAccessKey, PutUserPolicy, and related calls — to mint credentials and grant itself S3 administrative privileges. This fully compromises the confidentiality, integrity, and availability of stored objects.
No credentials are required, and enabling the documented JWT signing keys does not close it: the IAM gRPC service was not gated by that mechanism. Even under mTLS, the listener-level allowed_commonNames ACL applies to the port rather than to individual RPCs, so any cluster mesh certificate could reach these administrative calls.
Affected component
weed/server/filer_server_handlers_iam_grpc.goweed/command/filer.go
Patches
Fixed in 4.24. Every IAM RPC now requires a Bearer token signed with the filer admin signing key (jwt.filer_signing.key), and the service refuses to register when no signing key is configured — removing the unauthenticated default entirely.
Workarounds
Restrict the filer gRPC port to trusted hosts. Configure jwt.filer_signing.key in security.toml and upgrade to 4.24; operators that use the IAM RPCs must attach an admin-signed Bearer token on each call.
References
- Fixed by seaweedfs/seaweedfs#9442 (follow-ups: #9498, #9508, #9514, #9536)
- Reported by Kadir Arslan (https://github.com/KadirArslan)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/seaweedfs/seaweedfs | all versions | 0.0.0-20260512171108-5e8f99f40a8ago get github.com/seaweedfs/seaweedfs@v0.0.0-20260512171108-5e8f99f40a8a |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/seaweedfs/seaweedfs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/seaweedfs/seaweedfs to 0.0.0-20260512171108-5e8f99f40a8a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2v6v-25fm-p4fg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2v6v-25fm-p4fg can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2v6v-25fm-p4fg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2v6v-25fm-p4fg in your dependencies?
O3 Security finds GHSA-2v6v-25fm-p4fg across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.