Security readout for executives and security teams
Plain-English summary
RustFS versions before 1.0.0-beta.2 can let a lower-privileged user with IAM import permission create hidden, attacker-chosen service account credentials under any identity, including root. That can turn limited access into persistent administrative control of object storage.
Executive priority
Treat this as an urgent storage-platform privilege escalation. Prioritize upgrade and IAM review for any RustFS deployment handling business data, backups, logs, or customer content.
Technical view
The vulnerable PUT /rustfs/admin/v3/import-iam endpoint improperly validates attacker-controlled parent, claims, accessKey, and secretKey fields. With ImportIAMAction, an attacker can bypass privilege boundaries and create a service account under root/minioadmin, resulting in persistent full administrative access. Fixed in RustFS 1.0.0-beta.2.
Likely exposure
Exposure is limited to RustFS deployments before 1.0.0-beta.2 where a user or integration has ImportIAMAction. Risk rises sharply if administrative APIs are reachable over a network by operators, automation, or compromised credentials.
Exploitation context
The CVE record does not indicate CISA KEV listing, and the provided sources do not report active exploitation. The vulnerability is still high urgency because exploitation requires only low privileges and no user interaction once ImportIAMAction is available.
Researcher notes
Evidence supports improper authorization and privilege-boundary validation in IAM import. Sources identify the affected endpoint, required permission, controllable fields, root parent impact, and fixed version. No public exploit status or detailed vendor mitigations beyond the fix are included in the provided bundle.
Mitigation direction
- Upgrade RustFS to 1.0.0-beta.2 or later.
- Limit ImportIAMAction to only trusted administrative identities.
- Review vendor advisory for any updated hardening guidance.
- Rotate credentials for suspicious or unnecessary service accounts.
- Restrict network access to RustFS administrative interfaces.
Validation and detection
- Inventory RustFS deployments and confirm exact running versions.
- Identify all users, roles, and integrations with ImportIAMAction.
- Review service accounts created before upgrade, especially root-linked accounts.
- Check IAM import activity in administrative audit logs.
- Verify upgraded systems no longer accept arbitrary parent identity assignment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-45043 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/rustfs/rustfs/security/advisories/GHSA-566f-q62r-wcr8CVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.