CVE-2026-22042
Improper IAM Permission Validation in RustFS Enables Privilege Escalation
Publication date: 2026-01-08
Last updated on: 2026-01-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rustfs | rustfs | to 1.0.0-alpha.79 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in RustFS involves incorrect authorization in the ImportIam admin API. Specifically, the ImportIam operation validates permissions using ExportIAMAction instead of the correct ImportIAMAction. This mistake allows a principal with only export permissions to perform import operations, which include privileged write actions like creating or updating users, groups, policies, and service accounts. As a result, unauthorized IAM modifications and privilege escalation can occur. [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized changes in the IAM system of RustFS, such as creating or modifying users, groups, policies, and service accounts without proper authorization. This can result in privilege escalation, allowing attackers to gain higher-level access and control over the system, potentially compromising the security and integrity of the storage environment. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to perform an Import IAM operation using credentials that only have ExportIAM permissions. Specifically, you can test if the ImportIam admin API incorrectly authorizes import actions with export-only credentials. A proof of concept involves preparing a valid IAM import ZIP archive (e.g., containing a new administrative policy and a user or service account bound to that policy) and sending it to the Import IAM endpoint authenticated with export-only credentials. If the import succeeds, the system is vulnerable. Commands would involve using HTTP tools (like curl) or RustFS client commands to send the import request with export-only credentials and observe if the import is accepted. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade RustFS to version 1.0.0-alpha.79 or later, where the issue is fixed by correctly validating ImportIam permissions using ImportIAMAction instead of ExportIAMAction. Until the upgrade can be applied, restrict export-only IAM credentials from accessing the ImportIam admin API to prevent unauthorized import operations. [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not specify how this vulnerability impacts compliance with common standards and regulations such as GDPR or HIPAA.