How broadly exploitable is this vulnerability in a typical RustFS deployment?

Exploitability depends on how widely RustFS IAM and identity-management APIs are exposed internally. In environments where many services or users have restricted service accounts or STS credentials with the ability to create or manage other identities, the vulnerability can be widely exploitable. In tightly locked-down deployments with very limited access to IAM operations, the practical exposure is narrower, but the impact of a single compromised identity may still be severe.

What level of access does an attacker need to exploit this issue?

The attacker needs valid RustFS credentials—typically a restricted service account or STS-based temporary token—that can invoke service-account or identity-management operations. They do not need pre-existing administrator-level privileges; the flaw allows escalation from a constrained identity to an effectively unrestricted one.

What is the safest general fix pattern for this class of IAM bug?

The safest fix pattern is to centralize and harden authorization logic so that: - All identity-creation and credential-issuance paths go through a single, consistent policy engine. - The effective permissions of any newly minted identity are never broader than the permissions of the creator, after applying all session, inline, and resource policies. - Explicit allow decisions are required, and no "implicit allow unless denied" shortcuts are used for sensitive operations.

Severity:

CRITICAL RISK

(9.8)

Privilege Escalation via Flawed IAM Policy Evaluation (CWE-269) in RustFS

CVE-2026-22043

Published:

Jan 8, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-306

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

Account Takeover / Loss of Account Control

February 17, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Remote Code Execution on the Server Host

February 17, 2026

Vulnerability Type

Category:

Authorization and Access Control

CWE:

CWE-269;CWE-284;CWE-522

Impact:

Privilege Escalation and Access Control Bypass

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Authorization and Access Control

CWE:

CWE-269;CWE-284;CWE-522

Impact:

Privilege Escalation and Access Control Bypass

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Privilege Escalation via Flawed IAM Policy Evaluation (CWE-269) in RustFS

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.8)

Missing Authentication for Forgot-Password Email Change API (CWE-306)

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in node-sonos-http-api TTS Provider for macOS

Vulnerability Type

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare