Security readout for executives and security teams
Plain-English summary
SeaweedFS versions before 4.24 allow an unauthenticated party with network access to a volume server’s gRPC port to make the server contact internal or cloud-only systems and return their responses. This could expose cloud metadata, IAM credentials, or sensitive internal services.
Executive priority
Treat as an immediate remediation item wherever affected gRPC ports are reachable. Prioritize cloud-hosted and multi-tenant environments because successful abuse may disclose credentials and enable access to otherwise isolated services. Upgrade promptly and investigate possible metadata or internal-service access.
Technical view
The unauthenticated VolumeServer.FetchAndWriteNeedle RPC accepts a caller-controlled remote endpoint without target validation. It can reach loopback, link-local, private-network, and cloud metadata addresses, then store and expose the response. Documented JWT signing keys do not protect this RPC. CVSS 3.1 rates it 9.3.
Likely exposure
Exposure requires SeaweedFS earlier than 4.24 and attacker reachability to a volume server’s gRPC port. Cloud deployments face particular credential risk. Private deployments remain vulnerable where untrusted users or compromised workloads can reach that port.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation is nevertheless low-complexity, requires no authentication or user interaction, and can cross security boundaries when the gRPC service is reachable.
Researcher notes
This is CWE-918 SSRF with response read-back and a changed security scope. The important control boundary is network reachability to the unauthenticated gRPC method; configured JWT signing keys are not sufficient. The bundle identifies the fix commit and 4.24 release but provides no evidence of exploitation in the wild.
Mitigation direction
- Upgrade every affected SeaweedFS volume server to version 4.24 or later.
- Restrict volume-server gRPC access to explicitly trusted systems while upgrading.
- Limit volume-server outbound access to metadata, loopback, private, and sensitive internal destinations.
- Review the vendor advisory and release notes for deployment-specific guidance.
Validation and detection
- Inventory SeaweedFS versions and identify every instance earlier than 4.24.
- Map which users, workloads, and networks can reach each volume server’s gRPC port.
- Confirm all volume servers run version 4.24 or later after remediation.
- Review cloud IAM and metadata-access logs for unexpected requests from volume servers.
- Check internal service logs for anomalous requests originating from volume-server hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-73080 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N3.94.7GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.3CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-87fv-vqqr-m4jrCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/seaweedfs/seaweedfs/pull/9441CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/seaweedfs/seaweedfs/commit/69da20bdaec923e5a43d8aa71bf3c0a2051fc019CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/seaweedfs/seaweedfs/releases/tag/4.24CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.