SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.8epss 0.4%
from disclosure to weapon41 days
Published on NVDJun 25
1st PoC+41d
exploitation probability
0.4%top 69% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
SeaweedFS is a distributed storage system for object storage (S3), file systems, and Iceberg tables. Prior to 4.30, the S3 API gateway and the Iceberg REST catalog gateway construct their routers with mux.NewRouter().SkipClean(true). With path cleaning disabled, a .. segment inside the URL survives routing, so a request such as `GET /bucket-A/../evil-bucket/key`, is matched as bucket=bucket-A, object=../evil-bucket/key. The captured object key is then joined into a filer path with util.JoinPath (S3) / path.Join (Iceberg), which collapse the .. server-side, so the actual read or write lands in evil-bucket. This vulnerability is fixed in 4.30.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
Affected products
seaweedfs · seaweedfspublic PoCs found — 1
githubgithub.com/BiiTts/CVE-2026-54917-SeaweedFS-Cross-Bucket-Traversal★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.