All vulnerabilities

Servers and applications

GHSA-jw56-gm6j-34mp

Standalone `weed iam` server grants any broad-policy S3 identity full IAM administration rights, allowing privilege escalation to admin

Severity
Critical
Published
2 Sept 2026
Last changed
2 Sept 2026
Added to UpHeron
22 Oct 2026
Sources
Project advisories (GitHub)

Description

The standalone weed iam server (deprecated but still shipped in v4.40) routes all IAM management actions through a single POST / endpoint. The authorization check always calls VerifyActionPermission with an empty bucket and object, which causes the policy evaluator to resolve the IAM management action to s3: against the resource ARN arn:aws:s3:::. Any policy statement containing Action: s3: and Resource: *, a routine grant for S3 data-plane access, matches both, so the check passes. An authenticated S3 identity with no IAM administration rights can create users, mint access keys for arbitrary accounts, and attach admin policies to itself.

  • Components running: master, volume, filer, and the standalone weed iam server
  • Attacker-reachable port: the weed iam HTTP port (default 8111)
  • Authentication: IAM auth active; identities loaded from a -config file or the filer credential store.
From seaweedfs/seaweedfs's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
SeaweedFSServers and applications · github:seaweedfs/seaweedfs
  • Every version up to 4.40

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

From Wikidata, CC0 1.0.
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

References