Servers and applications
GHSA-qmx6-fpcw-q3xg
S3 API: bucket policy not enforced on POST Object uploads — an S3 identity can overwrite another identity's data
- Severity
- Medium 6.5
- Published
- 23 Sept 2026
- Last changed
- 23 Sept 2026
- Added to UpHeron
- 22 Oct 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N- Sources
- Project advisories (GitHub)
Description
Summary
The SeaweedFS S3 gateway does not evaluate bucket policies on the POST Object upload path (PostPolicyBucketHandler — POST /{bucket} with Content-Type: multipart/form-data; the HTML-form / presigned-POST upload).
Authorization for POST Object is performed only with the coarse per-identity action check (identity.CanDo(ACTION_WRITE, bucket, "")) plus verification of the caller's POST-policy signature. The bucket-policy engine that runs for every other S3 request (authRequestWithAuthType → EvaluatePolicy / VerifyActionPermission) is never invoked.
Consequently, when a bucket policy is used to restrict an authenticated S3 identity — the standard S3 mechanism for isolating multiple tenants that share a bucket, confining an identity to a key prefix, requiring encryption, or restricting by source IP — that restriction is silently ineffective for POST Object uploads.
Affected software
| Software | Affected versions |
|---|---|
SeaweedFSServers and applications · github:seaweedfs/seaweedfs |
|
About SeaweedFS
Fast distributed storage system for blobs, objects, files, and data lake, for billions of files. Blob store has O(1) disk seek, cloud tiering
- Docker Hub pulls
- 42,221,853Docker Hub, 15 Nov 2026
- GitHub stars
- 36,070GitHub, 15 Nov 2026
- Forks
- 3,114GitHub, 15 Nov 2026
- Latest release
- 4.53GitHub, 15 Nov 2026
- Released
- 8 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- Written in
- GoWikidata
- First released
- 21 Apr 2015Wikidata
- First published on GitHub
- 14 Jul 2014GitHub
Website Source code Docker image
Vulnerabilities in SeaweedFS
- In our list
- 58
- Published in the last 12 months
- 58
- Critical, last 12 months
- 17
- High, last 12 months
- 26
- Known exploited
- 0
- CVE-2026-129851SeaweedFS before 4.42 SSRF via VolumeServer.FetchAndWriteNeedle Replica URLsMedium 6.9 16 Nov 2026
- CVE-2026-129852SeaweedFS before 4.42 File Existence Disclosure via VolumeServer.FetchAndWriteNeedleMedium 6.9 16 Nov 2026
- GHSA-g96f-g546-47xfS3 gateway gRPC port exposes the IAM and lifecycle admin services without authentication when no filer signing key is configured, allowing anyone with network access to add an admin identityHigh 9 Nov 2026
- GHSA-5vhw-52xr-8x4jSTS AssumeRoleWithWebIdentity ignores trust policies when policy.defaultEffect is AllowMedium 9 Nov 2026
- GHSA-8rrx-349w-6396S3: object-scoped Write grant can change bucket configuration via the prefix query parameterMedium 9 Nov 2026
- GHSA-54j8-2gxc-wr9hS3 gateway applies response header overrides (response-content-type, response-content-disposition) to anonymous requests, enabling stored XSS on publicly readable bucketsMedium 6.1 9 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-qmx6-fpcw-q3xg
- github.com https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-qmx6-fpcw-q3xg