SeaweedFS <= 4.29 - Path Traversal File Write
SeaweedFS versions through 4.29 build the S3 API and Iceberg REST catalog routers with mux.NewRouter().SkipClean(true), which disables URL path cleaning. A `..` segment in the request path therefore survives routing and reaches the handlers unnormalised, so a request such as `PUT /bucket-A/../evil-bucket/key` is matched as bucket=bucket-A with object=../evil-bucket/key. The captured object key is then joined into a filer path where the `..` is collapsed server-side, so the write lands in evil-bucket while authorisation is evaluated against bucket-A, enabling cross-bucket file write. References: https://github.com/advisories/GHSA-w62w-66v9-vvgv https://github.com/seaweedfs/seaweedfs/commit/dd1b4287899eed3dfd73c2f3b1de001996fda229 https://nvd.nist.gov/vuln/detail/CVE-2026-54917 Remediation: Upgrade to SeaweedFS 4.30 or later.
Used 20 times · 10 assets checked · domain, subdomain, ipv4