Approved changes feed: RSS · Atom

cpe:2.3:a:seaweedfs:seaweedfs:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorSeaweedfs (8822ac32-8ab0-55b4-b1b0-281f1b3c98c0)
ProductSeaweedfs (7a010d7a-7cf4-5cab-a862-668da4db742a)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/seaweedfs/seaweedfs purl2cpe 2026-06-01 10:10:56.263551
pkg:golang/github.com/seaweedfs/seaweedfs purl2cpe 2026-06-01 10:10:56.263554

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-100413 vulnerable 2026-11-03 10:15:33.216173 SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments
SeaweedFS is a distributed storage system for files and blobs. From 4.0.388 until 4.41, the SFTP Helm chart embedded one unencrypted Ed25519 private host key in k8s/charts/seaweedfs/templates/sftp/sftp-secret.yaml as stringData.seaweedfs_sftp_ssh_private_key. A standalone deployment presented that public key when sftp.enabled and sftp.enableAuth were true, sftp.existingConfigSecret was not supplied, the legacy sftp.sshPrivateKey path remained selected, a valid config-ssh Secret allowed startup, and hostKeysFolder did not provide a later Ed25519 signer. An attacker able to redirect or intercept client traffic could impersonate that SFTP endpoint to clients that trusted the published host identity, exposing password credentials or data sent to the rogue endpoint. Default all-in-one and non-authenticated standalone paths did not load the key. This issue is fixed in version 4.41.
Published: 2026-10-14T18:03:12.709Z
Updated: 2026-10-29T13:52:32.572Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-73080 vulnerable 2026-09-16 04:33:09.987317 SeaweedFS: Unauthenticated SSRF with response read-back via VolumeServer.FetchAndWriteNeedle
CRITICAL (9.3)
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.
Published: 2026-08-11T15:57:10.809Z
Updated: 2026-08-13T14:53:42.133Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-72920 vulnerable 2026-09-16 04:33:08.284365 SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
CRITICAL (9.8)
SeaweedFS is a distributed storage system. Prior to 4.24, the filer registers the SeaweedIdentityAccessManagement gRPC service without mandatory authentication when jwt.filer_signing.key is unset, allowing any client that can reach the filer gRPC port to invoke CreateUser, CreateAccessKey, PutPolicy, and related IAM RPCs to mint credentials and gain S3 administrative control. This issue is fixed in versions 4.24.
Published: 2026-08-11T14:23:22.425Z
Updated: 2026-08-11T14:46:46.118Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-58372 vulnerable 2026-07-29 01:03:16.771320 SeaweedFS < 4.34 - Cross-Bucket Object Deletion via DeleteObjects Request-Body Keys
HIGH (8.1)
SeaweedFS before 4.34 contains a path traversal vulnerability in the S3 gateway DeleteMultipleObjectsHandler that allows authenticated S3 principals with write access to a single bucket to delete arbitrary objects in other tenants' buckets by supplying object keys containing ../ sequences in the DeleteObjects XML request body. Attackers can bypass authorization controls through a confused deputy condition, as the validateRequestPath middleware only inspects URL-captured path variables and never examines request-body keys, allowing the filer path to collapse directory traversal sequences and resolve deletions outside the authorized bucket.
Published: 2026-06-30T15:57:59.372Z
Updated: 2026-11-08T14:06:57.487Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-58371 vulnerable 2026-07-29 01:03:16.771009 SeaweedFS < 4.30 - Cross-Origin Information Disclosure via Unvalidated JSONP callback Parameter
LOW (3.1)
SeaweedFS before 4.30 reflects the callback query parameter verbatim into responses served with Content-Type application/javascript in the shared writeJson helper (weed/server/common.go), with no callback-name validation, no X-Content-Type-Options: nosniff header, and no CORS allow-list. Every JSON endpoint that uses writeJson - including the unauthenticated master endpoints /dir/status, /dir/lookup and /cluster/status, the volume server /status, and the filer directory listing, all reachable in the default configuration (no -whiteList, no security.toml, bound to 0.0.0.0) - can therefore be loaded cross-origin via a script tag with a chosen callback, letting a third-party web page read cluster topology, volume server URLs and gRPC ports, file identifiers, and directory listings. Because the callback string is reflected at the start of the body and no nosniff header is sent, MIME-sniffing clients may also interpret the reflected content as HTML.
Published: 2026-06-30T15:57:36.585Z
Updated: 2026-11-08T14:06:56.821Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-55874 vulnerable 2026-07-29 01:00:28.658165 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-55873 vulnerable 2026-07-29 01:00:28.657962 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-54917 vulnerable 2026-07-29 01:00:28.109433 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.