dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-45043

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RustFS is a distributed object storage system built in Rust. Prior to 1.0.0-beta.2, improper validation in the PUT /rustfs/admin/v3/import-iam endpoint allows a user with ImportIAMAction to create service accounts under arbitrary parent identities, including the root user (minioadmin). The endpoint accepts attacker-controlled parent, claims, accessKey, and secretKey values without enforcing privilege boundaries or sanitization. This enables privilege escalation to full administrative access using a persistent, attacker-defined credential. This vulnerability is fixed in 1.0.0-beta.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper validation in RustFS's PUT /rustfs/admin/v3/import-iam endpoint allows users with ImportIAMAction permissions to create service accounts under arbitrary parent identities, including the root user (minioadmin). The endpoint accepts attacker-controlled parent, claims, accessKey, and secretKey values without enforcing privilege boundaries or sanitization, enabling privilege escalation to full administrative access with persistent attacker-defined credentials.

MitigationUpgrade to RustFS version 1.0.0-beta.2 or later which implements proper validation and privilege boundary enforcement for the import-iam endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify RustFS installation and version
    Locate the RustFS binary or service and retrieve its version number using 'rustfs --version' or checking the service's version endpoint
    Affected if The installed version is before 1.0.0-beta.2 (e.g., 1.0.0-beta.1, 1.0.0-alpha.x, or any version number lower than 1.0.0-beta.2)
  2. Check for ImportIAMAction permission
    Review IAM/user policies or role definitions to determine if any user or service account has the ImportIAMAction permission enabled
    Affected if ImportIAMAction is granted to any user or service account, especially non-administrative ones
  3. Verify endpoint exposure
    Inspect API gateway, reverse proxy, or firewall rules to confirm the PUT /rustfs/admin/v3/import-iam endpoint is externally or internally accessible
    Affected if The /rustfs/admin/v3/import-iam endpoint is reachable from untrusted network segments or by non-admin users
  4. Review admin access controls
    Examine IAM parent identity configuration or admin role bindings to identify if arbitrary parent identities (including root/minioadmin) can be specified during import operations
    Affected if The system allows specification of arbitrary parent identities without validation during IAM import operations
  5. Audit recent import-iam activity
    Review access logs, audit trails, or security event logs for recent PUT requests to /rustfs/admin/v3/import-iam that created or modified administrative users or credentials
    Affected if There are log entries showing import-iam calls that created users with administrative privileges or modified critical IAM settings

You are affected if RustFS version is before 1.0.0-beta.2 AND the ImportIAMAction permission is enabled for any user, allowing potential privilege escalation through the import-iam endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to RustFS version 1.0.0-beta.2 or later which implements proper validation and privilege boundary enforcement for the import-iam endpoint.

Recommended fix Moderate confidence

1.0.0-beta.2

  1. 1. Identify the current version of RustFS deployed in your environment
  2. 2. If running a version prior to 1.0.0-beta.2, plan for upgrade to version 1.0.0-beta.2
  3. 3. Review the release notes for 1.0.0-beta.2 to understand changes and any required migration steps
  4. 4. Create a backup of current configuration and data
  5. 5. Upgrade RustFS to version 1.0.0-beta.2 following standard upgrade procedures
  6. 6. Verify the upgrade was successful and the service is operational
  7. 7. Review audit logs to determine if the vulnerability was exploited (check for unauthorized use of PUT /rustfs/admin/v3/import-iam endpoint)
  8. 8. If exploitation is suspected, rotate all credentials and review access controls
Caveat Review release notes for 1.0.0-beta.2; beta releases may have stability or compatibility considerations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45043 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data