RustFS: ListServiceAccount authorizes against wrong admin action, enabling cross-user enumeration and root service account takeover

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary ListServiceAccount (GET /rustfs/admin/v3/list-service-accounts?user=<other) authorizes cross-user requests against UpdateServiceAccountAdminAction instead of ListServiceAccountsAdminAction at rustfs/src/admin/handlers/serviceaccount.rs:936. The handler accepts the wrong admin action and rejects the correct one: - A user granted only admin:UpdateServiceAccount enumerates every service account in the cluster, including the root user's (HTTP 200, full metadata). - A user granted only admin:ListServiceAccounts — the permission name every IAM document treats as "list service accounts" — receives HTTP 403 AccessDenied on the same request. Because service account access keys act as the identifier a UpdateServiceAccount holder needs to rotate a secret, and the UpdateServiceAccount handler at rustfs/src/admin/handlers/serviceaccount.rs:489 performs no ownership check on the target access key, leaking those access keys lets a delegated "service account updater" role overwrite…

Published by the source

5 May 2026, 20:14 UTC

Last modified by the source

5 May 2026, 20:14 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mm2q-qcmx-gw4w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-mm2q-qcmx-gw4w

Advisory: RustFS: ListServiceAccount authorizes against wrong admin action, enabling cross-user enumeration and root service account takeover
IDs: GHSA-mm2q-qcmx-gw4w
Record: https://patchnext.com/advisories/ghsa-mm2q-qcmx-gw4w (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rustfs 1.0.0-alpha.98. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rustfs: affected <= 1.0.0-alpha.91; fixed in 1.0.0-alpha.98

## Suggested inspection (read-only)
- crates.io rustfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rustfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mm2q-qcmx-gw4w (GitHub-reviewed advisory GHSA-mm2q-qcmx-gw4w lists affected ranges: crates.io rustfs >=0 <=1.0.0-alpha.91)

Commands are suggestions: review each one before running it.