# CVE-2026-73080: SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle

> Unauthenticated attackers can trigger Server-Side Request Forgery in SeaweedFS to access internal services and cloud metadata, exposing sensitive credentials.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** BIT-seaweedfs-2026-73080, GHSA-87fv-vqqr-m4jr, GO-2026-6219, MINI-4rj9-c4f5-pfr2, MINI-999h-rh72-w2r4

## What is CVE-2026-73080?

CVE-2026-73080 is a critical server-side request forgery vulnerability in seaweedfs, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SeaweedFS is a distributed storage system. Prior to 4.24, VolumeServer.FetchAndWriteNeedle in weed/server/volume_grpc_remote.go fetches a caller-supplied remote endpoint through weed/remote_storage/s3/s3_storage_client.go and writes the response into a needle. The RPC performs no authentication and no target validation, allowing anyone who can reach a volume server's gRPC port to cause requests to arbitrary hosts, including loopback, link-local, RFC 1918, and cloud metadata endpoints such as 169.254.169.254, and read the response. On cloud deployments, this can disclose instance metadata and IAM credentials and reach otherwise unexposed internal services. The volume server gRPC plane is unauthenticated by default, and configuring documented JWT signing keys does not protect this RPC. This issue is fixed in version 4.24.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-73080?

4 open source packages ship an affected version, including github.com/seaweedfs/seaweedfs and seaweedfs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171120-69da20bdaec9 |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171120-69da20bdaec9 |
| `github.com/seaweedfs/seaweedfs` | Go | All versions | 0.0.0-20260512171120-69da20bdaec9 |
| `seaweedfs` | Bitnami | All versions | 4.24.0 |

## How do I fix CVE-2026-73080?

Upgrade github.com/seaweedfs/seaweedfs to 0.0.0-20260512171120-69da20bdaec9 or later.

## Is CVE-2026-73080 being exploited?

There is no known exploitation of CVE-2026-73080 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73080 and fix it if it is affected.

What it is: CVE-2026-73080 is a critical server-side request forgery vulnerability in seaweedfs, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-73080 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171120-69da20bdaec9
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171120-69da20bdaec9
- github.com/seaweedfs/seaweedfs (Go): affected all versions; fixed in 0.0.0-20260512171120-69da20bdaec9
- seaweedfs (Bitnami): affected all versions; fixed in 4.24.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73080/ (Markdown: https://insights.sbomify.com/CVE-2026-73080/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73080
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73080
- OSV: https://osv.dev/vulnerability/CVE-2026-73080

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73080/
Summaries are generated and may contain mistakes; the official description above is the record.