{"id":"GHSA-87fv-vqqr-m4jr","revision":"692f2ac5cdff4e1f9d0d68a75549e64d","records":[{"revision":"692f2ac5cdff4e1f9d0d68a75549e64d","observedAt":"2026-10-24T13:19:41.952+00:00","statement":{"source":"osv","id":"GHSA-87fv-vqqr-m4jr","aliases":["BIT-seaweedfs-2026-73080","CVE-2026-73080","GO-2026-6219"],"title":"SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle","description":"### Impact\n`VolumeServer.FetchAndWriteNeedle` fetches a caller-supplied remote endpoint and writes the response into a needle. Before 4.24 this RPC performed no authentication and no validation of the target, so anyone able to reach a volume server's gRPC port could coerce the server into issuing requests to arbitrary hosts — including loopback, link-local, RFC 1918, and cloud metadata endpoints such as `169.254.169.254` — and read the response back. On cloud deployments this discloses instance metadata and IAM credentials, and can be used to reach otherwise-unexposed internal services (SSRF with response read-back).\n\nThe volume server gRPC plane is unauthenticated on a default deployment, so no credentials are required. Configuring the documented JWT signing keys does not close it, because that hardening does not apply to this RPC.\n\n### Affected component\n- `weed/server/volume_grpc_remote.go` (`FetchAndWriteNeedle`)\n- `weed/remote_storage/s3/s3_storage_client.go`\n\n### Patches\nFixed in **4.24**. `FetchAndWriteNeedle` now requires admin authorization and refuses loopback / link-local / RFC 1918 / IMDS destinations through a guarded dialer that resolves the host itself and pins the resolved address for the duration of the request, defeating DNS-rebinding. The Rust volume server carries the equivalent endpoint validation.\n\n### Workarounds\nRestrict volume server gRPC ports to trusted hosts via firewall / network policy, and enable mTLS via `security.toml`.","state":0,"publishedAt":"2026-08-11T15:58:23+00:00","modifiedAt":"2026-08-18T15:11:03.4878581+00:00","affected":[{"ecosystem":"Go","name":"github.com/seaweedfs/seaweedfs","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"0"},{"kind":"fixed","version":"0.0.0-20260512171120-69da20bdaec9"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"CRITICAL"}],"references":["https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-87fv-vqqr-m4jr","https://github.com/seaweedfs/seaweedfs/pull/9441","https://github.com/seaweedfs/seaweedfs/commit/69da20bdaec923e5a43d8aa71bf3c0a2051fc019","https://github.com/seaweedfs/seaweedfs","https://github.com/seaweedfs/seaweedfs/releases/tag/4.24"],"sourceUrl":"https://github.com/advisories/GHSA-87fv-vqqr-m4jr","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-87fv-vqqr-m4jr","identifiers":["GHSA-87fv-vqqr-m4jr","BIT-seaweedfs-2026-73080","CVE-2026-73080","GO-2026-6219"]},"retained":false,"historicalAffected":[]}],"coverage":[]}