dbcve.org
RustfsApplication

CVE-2026-22043

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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. In versions 1.0.0-alpha.13 through 1.0.0-alpha.78, a flawed `deny_only` short-circuit in RustFS IAM allows a restricted service account or STS credential to self-issue an unrestricted service account, inheriting the parent’s full privileges. This enables privilege escalation and bypass of session/inline policy restrictions. Version 1.0.0-alpha.79 fixes the issue.

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

A flawed deny_only short-circuit in RustFS IAM allows a restricted service account or STS credential to self-issue an unrestricted service account, inheriting the parent's full privileges. This enables privilege escalation by bypassing session and inline policy restrictions.

MitigationUpgrade to RustFS version 1.0.0-alpha.79 or later. Review and audit existing service accounts and STS credentials to detect any instances of privilege escalation that may have occurred.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RustfsApplication
Affected:= 1.0.0

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed RustFS version
    Run 'rustfs --version' or check the version metadata of the rustfs binary/package in your environment
    Affected if The installed version is exactly 1.0.0 (the only affected version listed)
  2. Locate IAM deny_only configuration
    Inspect RustFS IAM configuration files or run 'rustfs iam get-config' to retrieve the deny_only short-circuit settings
    Affected if deny_only is enabled and allows service account self-issuance without session policy validation
  3. Audit service account creation logs
    Review RustFS audit logs for 'CreateServiceAccount' or 'AssumeRole' operations where the principal matches the target service account (self-issuance pattern)
    Affected if Logs show a restricted service account successfully creating or assuming an unrestricted service account with elevated privileges
  4. Examine STS credential delegation paths
    Query IAM policy evaluation logs for STS credentials that issued new credentials bypassing inline or session policy restrictions
    Affected if STS credentials were able to escalate privileges by creating unrestricted service accounts that inherited full parent privileges

You are affected if RustFS version 1.0.0 is running with deny_only IAM enabled and evidence shows service accounts or STS credentials have performed self-issuance bypassing policy restrictions.

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-alpha.79 or later. Review and audit existing service accounts and STS credentials to detect any instances of privilege escalation that may have occurred.

Recommended fix High confidence

Upgrade to Rustfs version 1.0.0-alpha.79 or later

  1. Identify all deployments or systems using Rustfs versions 1.0.0-alpha.13 through 1.0.0-alpha.78
  2. Locate the dependency configuration file (e.g., Cargo.toml) where Rustfs is declared
  3. Update the Rustfs dependency version to 1.0.0-alpha.79 or later (e.g., rustfs = "1.0.0-alpha.79")
  4. Run cargo update or cargo build to fetch the new version
  5. Verify the new version is correctly installed by checking cargo.lock
  6. Re-run any existing tests to ensure the upgrade does not break functionality
  7. Deploy the updated application to all affected environments
Caveat Alpha releases may have breaking changes; review release notes for any API modifications between your current version and 1.0.0-alpha.79

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

Fix this in Rustfs Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22043 — 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-22043 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