CVE-2025-62506 MinIO vulnerable to privilege escalation via session policy bypass in service accounts and STS

High 8.1 Published Updated

Attackers with restricted service or STS credentials can bypass policy restrictions to create unrestricted accounts, gaining unauthorized access to modify or delete data.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-62506?

CVE-2025-62506 is a high-severity vulnerability in minio, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

MinIO is a high-performance object storage system. In all versions prior to RELEASE.2025-10-15T17-29-55Z, 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 operations on their own account, specifically when creating new service accounts for the same user. The vulnerability exists in the IAM policy validation logic where the code incorrectly relied on the DenyOnly argument when validating session policies for restricted accounts. When a session policy is present, the system should validate that the action is allowed by the session policy, not just that it is not denied. An attacker with valid credentials for a restricted service or STS account can create a new service account for itself without policy restrictions, resulting in a new service account with full parent privileges instead of being restricted by the inline policy. This allows the attacker to access buckets and objects beyond their intended restrictions and modify, delete, or create objects outside their authorized scope. The vulnerability is fixed in version RELEASE.2025-10-15T17-29-55Z.

Weakness: CWE-863

Which versions are affected by CVE-2025-62506?

3 open source packages ship an affected version, including github.com/minio/minio.

PackageAffectedFixed in
github.com/minio/minio GoAll versions0.0.0-20251015170045-c1a49490c78e
github.com/minio/minio GoAll versions0.0.0-20251015170045-c1a49490c78e
github.com/minio/minio GoAll versions0.0.0-20251015170045-c1a49490c78e

How do I fix CVE-2025-62506?

Upgrade github.com/minio/minio to 0.0.0-20251015170045-c1a49490c78e or later.

Is CVE-2025-62506 being exploited?

There is no known exploitation of CVE-2025-62506 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-jjjj-jwhf-8rgr, GO-2025-4034, MINI-r348-f45c-c4fx, MINI-w975-883j-fg87.

Is CVE-2025-62506 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free