Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-jjjj-jwhf-8rgr
No affected components available
Summary
A privilege escalation vulnerability allows service accounts and STS (Security Token Service) accounts with restricted session policies to bypass their inline policy restrictions when performing "own" account operations, specifically when creating new service accounts for the same user.
Details
The vulnerability exists in the IAM policy validation logic in cmd/iam.go. When validating session policies for restricted accounts performing operations on their own account (such as creating service accounts), the code incorrectly relied on the DenyOnly argument.
The DenyOnly flag is used to allow accounts to perform actions related to their own account by only checking if the action is explicitly denied. However, when a session policy (sub-policy) is present, the system should validate that the action is actually allowed by the session policy, not just that it isn't denied.
Attack Scenario
- An administrator creates a service account or STS account with a restricted inline policy (e.g., access only to bucket1 and bucket2)
- The restricted account attempts to create a new service account for itself without specifying any policy restrictions
- Due to the bypass, the new service account is created with full parent privileges instead of being restricted by the inline policy
- The attacker now has escalated privileges beyond the intended restrictions
Impact
Attack Complexity: LOW - Exploitation requires only valid credentials for a restricted service/STS account
Confidentiality: HIGH - Attackers can access buckets and objects beyond their intended restrictions
Integrity: HIGH - Attackers can modify, delete, or create objects outside their authorized scope
Availability: NONE - Does not directly impact service availability
Patches
Fixed in PR https://github.com/minio/minio/pull/21642 Commit: c1a49490c78e9c3ebcad86ba0662319138ace190
Install the release
go install -v github.com/minio/minio@RELEASE.2025-10-15T17-29-55Z
Workarounds
No workarounds available. You can upgrade to the latest version immediately.
Mitigation Steps
- Upgrade MinIO: Update to the latest version containing the fix
- Audit Service Accounts: Review all service accounts created by non-admin accounts
- Revoke Suspicious Accounts: Delete any service accounts that may have been created through exploitation
- Review Access Logs: Check for unauthorized access to sensitive buckets
Resources
- Fix PR: https://github.com/minio/minio/pull/21642
- Affected code: cmd/iam.go (functions: isAllowedBySessionPolicyForServiceAccount, isAllowedBySessionPolicy)
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard