MinIO Operator STS is a native IAM Authentication for Kubernetes. Prior to version 7.1.0, if no audiences are provided for the `spec.audiences` field, the default will be of the Kubernetes apiserver. Without scoping, it can be replayed to other internal systems, which may unintentionally trust it. This issue has been patched in version 7.1.0.

Affected: Go: github.com/minio/operator

# Prevent token leakage / privilege escalation

## MinIO Operator STS: A Quick Overview

MinIO Operator STS is a native IAM Authentication for Kubernetes. MinIO Operator offers support for [Secure Tokens](https://min.io/docs/minio/linux/developers/security-token-service.html?ref=op-gh) (a.k.a. STS) which are a form of temporary access credentials for your MinIO Tenant. In essence, this allows you to control access to your MinIO tenant from your applications without having to explicitly create credentials for each application.

For an application to gain access into a MinIO Tenant, a `PolicyBinding` resource is required, granting explicit access to the applications by validating the kubernetes [Service Account](https://kubernetes.io/docs/concepts/security/service-accounts/) authorization token.

The service account token is validated as follows:

1. The application calls `AssumeRoleWithWebIdentity` API MinIO Operator provides. 2. MinIO Operator verifies the Service Account token agains the kubernetes API using the [TokenReview API](https://kubernetes.io/docs/reference/kubernetes-api/authentication-resources/token-review-v1/) 3. MinIO Operator reviews the TokenReviewResult confirms if the token is a valid token and the user is authenticated. 4. MinIO Operator validates the service account has `PolicyBinding` in the Tenant namespace. 5. MinIO Operator gets the PolicyBinding 6. MinIO Operator calls the AssumeRole API in the MinIO Tenant 7. MinIO Operator obtains temporary crede…

govulncheck-vulndb-0.0.20250422T181640-1.1 on GA media