GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-2V6V-25FM-P4FG

Vulnerability from github – Published: 2026-09-02 14:51 – Updated: 2026-09-02 14:51
VLAI
Summary
SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control
Details

Impact

The filer registered the IAM gRPC service (SeaweedIdentityAccessManagement) with no authentication. Any client able to reach the filer gRPC port could invoke IAM RPCs — CreateUser, CreateAccessKey, PutUserPolicy, and related calls — to mint credentials and grant itself S3 administrative privileges. This fully compromises the confidentiality, integrity, and availability of stored objects.

No credentials are required, and enabling the documented JWT signing keys does not close it: the IAM gRPC service was not gated by that mechanism. Even under mTLS, the listener-level allowed_commonNames ACL applies to the port rather than to individual RPCs, so any cluster mesh certificate could reach these administrative calls.

Affected component

  • weed/server/filer_server_handlers_iam_grpc.go
  • weed/command/filer.go

Patches

Fixed in 4.24. Every IAM RPC now requires a Bearer token signed with the filer admin signing key (jwt.filer_signing.key), and the service refuses to register when no signing key is configured — removing the unauthenticated default entirely.

Workarounds

Restrict the filer gRPC port to trusted hosts. Configure jwt.filer_signing.key in security.toml and upgrade to 4.24; operators that use the IAM RPCs must attach an admin-signed Bearer token on each call.

References

  • Fixed by seaweedfs/seaweedfs#9442 (follow-ups: #9498, #9508, #9514, #9536)
  • Reported by Kadir Arslan (https://github.com/KadirArslan)
Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/seaweedfs/seaweedfs"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20260512171108-5e8f99f40a8a"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-72920"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-02T14:51:58Z",
    "nvd_published_at": "2026-08-11T15:17:38Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\nThe filer registered the IAM gRPC service (`SeaweedIdentityAccessManagement`) with no authentication. Any client able to reach the filer gRPC port could invoke IAM RPCs \u2014 `CreateUser`, `CreateAccessKey`, `PutUserPolicy`, and related calls \u2014 to mint credentials and grant itself S3 administrative privileges. This fully compromises the confidentiality, integrity, and availability of stored objects.\n\nNo credentials are required, and enabling the documented JWT signing keys does not close it: the IAM gRPC service was not gated by that mechanism. Even under mTLS, the listener-level `allowed_commonNames` ACL applies to the port rather than to individual RPCs, so any cluster mesh certificate could reach these administrative calls.\n\n### Affected component\n- `weed/server/filer_server_handlers_iam_grpc.go`\n- `weed/command/filer.go`\n\n### Patches\nFixed in **4.24**. Every IAM RPC now requires a Bearer token signed with the filer admin signing key (`jwt.filer_signing.key`), and the service refuses to register when no signing key is configured \u2014 removing the unauthenticated default entirely.\n\n### Workarounds\nRestrict the filer gRPC port to trusted hosts. Configure `jwt.filer_signing.key` in `security.toml` and upgrade to 4.24; operators that use the IAM RPCs must attach an admin-signed Bearer token on each call.\n\n### References\n- Fixed by seaweedfs/seaweedfs#9442 (follow-ups: #9498, #9508, #9514, #9536)\n- Reported by Kadir Arslan (https://github.com/KadirArslan)",
  "id": "GHSA-2v6v-25fm-p4fg",
  "modified": "2026-09-02T14:51:59Z",
  "published": "2026-09-02T14:51:58Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/seaweedfs/seaweedfs/security/advisories/GHSA-2v6v-25fm-p4fg"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72920"
    },
    {
      "type": "WEB",
      "url": "https://github.com/seaweedfs/seaweedfs/pull/9442"
    },
    {
      "type": "WEB",
      "url": "https://github.com/seaweedfs/seaweedfs/commit/5e8f99f40a8abc7b449aefd260516443377041c7"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/seaweedfs/seaweedfs"
    },
    {
      "type": "WEB",
      "url": "https://github.com/seaweedfs/seaweedfs/releases/tag/4.24"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "SeaweedFS: Unauthenticated filer IAM gRPC service grants S3 administrative control"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.