Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/minio/operator

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.9GoPublished

    Minio Operator uses Kubernetes apiserver audience for AssumeRoleWithWebIdentity STS

    CVE-2025-32963 · GHSA-7m6v-q233-q9j9

    Affected
    • Go github.com/minio/operator < 7.1.0
    Fixed in
    7.1.0· Vendor fix available
    Issue
    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 (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 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 3. MinIO Operator reviews the TokenReviewResult confirms if the token is a valid token and the user is authenticated.…

    Recommended action: Upgrade to 7.1.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →