Servers and applications
CVE-2026-77611
Authenticated S3 object-scope bypass in PutObjectAcl allows overwriting a different object with the same basename
- Severity
- High 7.1
- Published
- 21 Aug 2026
- Last changed
- 21 Aug 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.39
- Exploit chance
- 0.4% in the next 30 daysHigher than 33% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Change data · Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L- Also known as
- GHSA-9x53-cjpr-m682
- Sources
- Project advisories (GitHub)
Description
An authenticated S3 principal with scoped write and ACL permissions for one object key can overwrite a different object outside that scope by calling PutObjectAcl on an object key containing a slash.
For example, a principal named scoped_writer is configured with permissions only for:
The same principal has no write or ACL permission for:
However, by calling PutObjectAcl on target-bucket/allowed/protected.txt, the principal can overwrite the content and metadata of target-bucket/protected.txt.
This bypasses object-level action scoping configured through the static S3 identity configuration file passed with -s3.config.
The issue is in the S3 PutObjectAclHandler.
The handler authorizes the request against the full requested object key. For a request targeting:
the permission check is performed against the intended scoped object path.
Later, when writing the updated entry back to the filer, the handler sets the update directory to the bucket root for non-versioned objects:
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
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-77611
- GitHub Advisory Database https://github.com/advisories/GHSA-9x53-cjpr-m682
- github.com https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-9x53-cjpr-m682