Skip to main content
Menu
CVEs

CVE

SeaweedFS unauthenticated SSRF in FetchAndWriteNeedle gRPC

CVE-2026-129851EUVD-2026-126409GHSA-CH4W-66X3-8V8X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

6.9MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 4.42
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.42.

Published
Last modified
Reference
Last checked
52/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: yes
  • Technical impact: partial

Summary

SeaweedFS (the product named in the affected facts) before the fixed release has a server-side request forgery flaw in the VolumeServer.FetchAndWriteNeedle gRPC method. An attacker can reach it remotely, without logging in, and make the volume server send requests with attacker-chosen tokens and bodies to internal services and metadata addresses.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

SeaweedFS before 4.42 contains a server-side request forgery vulnerability in the VolumeServer.FetchAndWriteNeedle gRPC method that allows unauthenticated attackers to bypass the incomplete CVE-2026-73080 fix. Attackers can supply crafted replicas[].url entries or an azure_endpoint to make the volume server send requests with controlled tokens and bodies to internal services and metadata addresses.

cve.now Index

52Pcve.now Index 52 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach10/20Affects Go packages
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 57 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.42.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129851 (SeaweedFS before 4.42 SSRF via VolumeServer.FetchAndWriteNeedle Replica URLs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129851 (entry last updated 2026-11-16):
Affected:
- Go package github.com/seaweedfs/seaweedfs: fixed in 4.42
Fixed versions: 4.42.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129851 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129851 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-939f-xh28-2q48
- https://github.com/seaweedfs/seaweedfs/commit/d713ab49f9c18f2188cdce2350f4ab95d19e2f17
- https://github.com/seaweedfs/seaweedfs/commit/9125b9c835f356c5b32469fa86215125b0ef7932
- https://github.com/seaweedfs/seaweedfs/releases/tag/4.42
- https://github.com/seaweedfs/seaweedfs/blob/de34a1a87c02893507f961cda9574172ee5064e9/weed/server/volume_grpc_remote.go#L258-L287
- https://www.vulncheck.com/advisories/seaweedfs-before-4.42-ssrf-via-volumeserver-fetchandwriteneedle-replica-urls
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129851
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129851"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 8

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 5

  1. Patch
  2. Patch
  3. Repository
  4. Repository
  5. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129851

Is CVE-2026-129851 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129851?

github.com/seaweedfs/seaweedfs (Go): before 4.42.Source: cve.now feed data

How do I fix CVE-2026-129851?

Upgrade to a fixed version: 4.42.Source: cve.now feed data