CVE-2026-73080: SeaweedFS Unauthenticated SSRF With Response Read-back Vulnerability

CRITICAL
Advisory Identifier: GHSA-87fv-vqqr-m4jr
Share
CVSS 9.3
CWE-918
Published
Advisory Summary

CVE-2026-73080 is a CRITICAL (CVSS 9.3) unauthenticated ssrf with response read-back vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting SeaweedFS libraries in the Go ecosystem. The issue involves unauthenticated ssrf with response read-back via volumeserver.fetchandwriteneedle. Remediation is available by upgrading affected packages to version 0.0.0-20260512171120-69da20bdaec9.

CVE-2026-73080 at a Glance

CVE Identifier CVE-2026-73080
GHSA Identifier GHSA-87fv-vqqr-m4jr
Severity CRITICAL
CVSS v3.1 Base Score 9.3
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product SeaweedFS
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 9.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-73080

To remediate this vulnerability, upgrade all affected SeaweedFS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/seaweedfs/seaweedfs fixed: 0.0.0-20260512171120-69da20bdaec9 
Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171120-69da20bdaec9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/seaweedfs/seaweedfs

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-73080, inspect your project dependencies for SeaweedFS:

inspect dependencies for github.com/seaweedfs/seaweedfs

Analyze the terminal output to locate any version of SeaweedFS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260512171120-69da20bdaec9), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In SeaweedFS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `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). The 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. ### Affected component - `weed/server/volume_grpc_remote.go` (`FetchAndWriteNeedle`) - `weed/remote_storage/s3/s3_storage_client.go` ### Patches Fixed 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. ### Workarounds Restrict volume server gRPC ports to trusted hosts via firewall / network policy, and enable mTLS via `security.toml`.

CVE-2026-73080 Affected SeaweedFS Versions

1 component(s)
Fixed Versions:
0.0.0-20260512171120-69da20bdaec9
Product / Package Ecosystem Affected Versions Fixed Version
github.com/seaweedfs/seaweedfs
golang/github.com/seaweedfs/seaweedfs
Go
< 0.0.0-20260512171120-69da20bdaec9
0.0.0-20260512171120-69da20bdaec9

References

GitHub Advisory / Wiki ADVISORY
https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-87fv-vqqr-m4jr
SeaweedFS Source Repository REPOSITORY
https://github.com/seaweedfs/seaweedfs/pull/9441
Security Fix Commit FIX COMMIT
https://github.com/seaweedfs/seaweedfs/commit/69da20bdaec923e5a43d8aa71bf3c0a2051fc019
SeaweedFS Source Repository REPOSITORY
https://github.com/seaweedfs/seaweedfs
SeaweedFS Release RELEASE
https://github.com/seaweedfs/seaweedfs/releases/tag/4.24

Frequently Asked Questions

What is CVE-2026-73080?
CVE-2026-73080 is a security vulnerability in SeaweedFS involving Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle under CWE-918: Server-Side Request Forgery (SSRF).
Which SeaweedFS versions are affected?
Affected versions include releases prior to 0.0.0-20260512171120-69da20bdaec9 across affected packages: github.com/seaweedfs/seaweedfs.
What version fixes CVE-2026-73080?
Upgrading to 0.0.0-20260512171120-69da20bdaec9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/seaweedfs/seaweedfs affected?
Yes, github.com/seaweedfs/seaweedfs is affected in releases prior to 0.0.0-20260512171120-69da20bdaec9. Upgrade your dependency to 0.0.0-20260512171120-69da20bdaec9 or later.
What is the CVSS score of CVE-2026-73080?
CVE-2026-73080 has a CVSS v3.1 base score of 9.3 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N.
What CWE is associated with CVE-2026-73080?
CVE-2026-73080 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2026-73080?
Run the dependency tree command: 'inspect dependencies for github.com/seaweedfs/seaweedfs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-87fv-vqqr-m4jr",
  "modified" : "2026-08-11T15:58:23Z",
  "published" : "2026-08-11T15:58:23Z",
  "aliases" : [ "CVE-2026-73080" ],
  "summary" : "SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle",
  "details" : "### 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`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/seaweedfs/seaweedfs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260512171120-69da20bdaec9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-87fv-vqqr-m4jr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/seaweedfs/seaweedfs/pull/9441"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/seaweedfs/seaweedfs/commit/69da20bdaec923e5a43d8aa71bf3c0a2051fc019"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/seaweedfs/seaweedfs"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/seaweedfs/seaweedfs/releases/tag/4.24"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-11T15:58:23Z",
    "nvd_published_at" : null
  }
}