Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle

CVE-2026-73080GHSA-87fv-vqqr-m4jr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/seaweedfs/seaweedfs 0.0.0-20260512171120-69da20bdaec9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-73080: 0.53% estimated exploitation activity in the next 30 days; percentile 44.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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/volumegrpcremote.go (FetchAndWriteNeedle) - weed/remotestorage/s3/s3storageclient.go Patches Fixed in 4.24. FetchAndWriteNeedle…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-87fv-vqqr-m4jr

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6219

  3. Revision 1 · created ·

    Published from osv record GHSA-87fv-vqqr-m4jr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73080

Advisory: SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle
IDs: CVE-2026-73080, GHSA-87fv-vqqr-m4jr
Record: https://patchnext.com/advisories/cve-2026-73080 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/seaweedfs/seaweedfs 0.0.0-20260512171120-69da20bdaec9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/seaweedfs/seaweedfs: affected < 0.0.0-20260512171120-69da20bdaec9; fixed in 0.0.0-20260512171120-69da20bdaec9

## Suggested inspection (read-only)
- Go github.com/seaweedfs/seaweedfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/seaweedfs/seaweedfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-87fv-vqqr-m4jr (OSV record GHSA-87fv-vqqr-m4jr lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260512171120-69da20bdaec9 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6219 (OSV record GO-2026-6219 lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260512171120-69da20bdaec9 (fixed))
- Verified: https://github.com/advisories/GHSA-87fv-vqqr-m4jr (GitHub-reviewed advisory GHSA-87fv-vqqr-m4jr lists affected ranges: Go github.com/seaweedfs/seaweedfs >=0 <0.0.0-20260512171120-69da20bdaec9)

Commands are suggestions: review each one before running it.

Loading voting…