CVE-2025-62506: Github.com/minio/minio MinIO Is Vulnerable To Privilege Vulnerability

HIGH
Advisory Identifier: GHSA-jjjj-jwhf-8rgr
CVSS 8.1
CWE-863
Published
Advisory Summary

CVE-2025-62506 is a HIGH (CVSS 8.1) minio is vulnerable to privilege vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/minio/minio libraries in the Go ecosystem. The issue involves minio is vulnerable to privilege escalation via session policy bypass in service accounts and sts. Remediation is available by upgrading affected packages to version 0.0.0-20251015170045-c1a49490c78e.

CVE-2025-62506 at a Glance

CVE Identifier CVE-2025-62506
GHSA Identifier GHSA-jjjj-jwhf-8rgr
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/minio/minio
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-62506

To remediate this vulnerability, upgrade all affected Github.com/minio/minio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/minio/minio fixed: 0.0.0-20251015170045-c1a49490c78e
Upgrade github.com/minio/minio to 0.0.0-20251015170045-c1a49490c78e
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/minio/minio

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-62506, inspect your project dependencies for Github.com/minio/minio:

inspect dependencies for github.com/minio/minio

Analyze the terminal output to locate any version of Github.com/minio/minio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20251015170045-c1a49490c78e), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/minio/minio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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 1. An administrator creates a service account or STS account with a restricted inline policy (e.g., access only to bucket1 and bucket2) 2. The restricted account attempts to create a new service account for itself without specifying any policy restrictions 3. Due to the bypass, the new service account is created with full parent privileges instead of being restricted by the inline policy 4. 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 1. **Upgrade MinIO**: Update to the latest version containing the fix 2. **Audit Service Accounts**: Review all service accounts created by non-admin accounts 3. **Revoke Suspicious Accounts**: Delete any service accounts that may have been created through exploitation 4. **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)

CVE-2025-62506 Affected Github.com/minio/minio Versions

1 component(s)
Fixed Versions:
0.0.0-20251015170045-c1a49490c78e
Product / Package Ecosystem Affected Versions Fixed Version
github.com/minio/minio
Go
< 0.0.0-20251015170045-c1a49490c78e
0.0.0-20251015170045-c1a49490c78e

References

Frequently Asked Questions

What is CVE-2025-62506?
CVE-2025-62506 is a security vulnerability in Github.com/minio/minio involving MinIO is Vulnerable to Privilege Escalation via Session Policy Bypass in Service Accounts and STS under CWE-863: Incorrect Authorization.
Which Github.com/minio/minio versions are affected?
Affected versions include releases prior to 0.0.0-20251015170045-c1a49490c78e across affected packages: github.com/minio/minio.
What version fixes CVE-2025-62506?
Upgrading to 0.0.0-20251015170045-c1a49490c78e (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/minio/minio affected?
Yes, github.com/minio/minio is affected in releases prior to 0.0.0-20251015170045-c1a49490c78e. Upgrade your dependency to 0.0.0-20251015170045-c1a49490c78e or later.
What is the CVSS score of CVE-2025-62506?
CVE-2025-62506 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2025-62506?
CVE-2025-62506 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2025-62506?
Run the dependency tree command: 'inspect dependencies for github.com/minio/minio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jjjj-jwhf-8rgr",
  "modified" : "2025-10-24T19:28:23Z",
  "published" : "2025-10-16T21:36:06Z",
  "aliases" : [ "CVE-2025-62506" ],
  "summary" : "MinIO is Vulnerable to Privilege Escalation via Session Policy Bypass in Service Accounts and STS",
  "details" : "### Summary\nA 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.\n\n### Details\nThe 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.\n\nThe `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.\n\n### Attack Scenario\n  1. An administrator creates a service account or STS account with a restricted inline policy (e.g., access only to bucket1 and bucket2)\n  2. The restricted account attempts to create a new service account for itself without specifying any policy restrictions\n  3. Due to the bypass, the new service account is created with full parent privileges instead of being restricted by the inline policy\n  4. The attacker now has escalated privileges beyond the intended restrictions\n\n### Impact\n\n  **Attack Complexity**: LOW - Exploitation requires only valid credentials for a restricted service/STS account\n\n  **Confidentiality**: HIGH - Attackers can access buckets and objects beyond their intended restrictions\n\n  **Integrity**: HIGH - Attackers can modify, delete, or create objects outside their authorized scope\n\n  **Availability**: NONE - Does not directly impact service availability\n\n### Patches\nFixed in PR https://github.com/minio/minio/pull/21642\nCommit: c1a49490c78e9c3ebcad86ba0662319138ace190\n\nInstall the release\n```\ngo install -v github.com/minio/minio@RELEASE.2025-10-15T17-29-55Z\n```\n\n### Workarounds\nNo workarounds available. You can upgrade to the latest version immediately.\n\n### Mitigation Steps\n\n1. **Upgrade MinIO**: Update to the latest version containing the fix\n2. **Audit Service Accounts**: Review all service accounts created by non-admin accounts\n3. **Revoke Suspicious Accounts**: Delete any service accounts that may have been created through exploitation\n4. **Review Access Logs**: Check for unauthorized access to sensitive buckets\n\n### Resources\n\n- Fix PR: https://github.com/minio/minio/pull/21642\n- Affected code: cmd/iam.go (functions: isAllowedBySessionPolicyForServiceAccount, isAllowedBySessionPolicy)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/minio/minio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20251015170045-c1a49490c78e"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/minio/minio/security/advisories/GHSA-jjjj-jwhf-8rgr"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-62506"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/minio/minio/issues/21647"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/minio/minio/pull/21642"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/minio/minio/commit/c1a49490c78e9c3ebcad86ba0662319138ace190"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/minio/minio"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/minio/minio/discussions/21655"
  }, {
    "type" : "WEB",
    "url" : "https://news.ycombinator.com/item?id=45684035"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-16T21:36:06Z",
    "nvd_published_at" : "2025-10-16T22:15:31Z"
  }
}