Minio Operator uses Kubernetes apiserver audience for AssumeRoleWithWebIdentity STS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-32963: 0.63% estimated exploitation activity in the next 30 days; percentile 50.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.…

Published by the source

21 Apr 2025, 22:51 UTC

Last modified by the source

23 Jan 2026, 17:16 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7m6v-q233-q9j9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-32963

Advisory: Minio Operator uses Kubernetes apiserver audience for AssumeRoleWithWebIdentity STS
IDs: CVE-2025-32963, GHSA-7m6v-q233-q9j9
Record: https://patchnext.com/advisories/cve-2025-32963 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/minio/operator 7.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/minio/operator: affected < 7.1.0; fixed in 7.1.0

## Suggested inspection (read-only)
- Go github.com/minio/operator: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/minio/operator.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7m6v-q233-q9j9 (GitHub-reviewed advisory GHSA-7m6v-q233-q9j9 lists affected ranges: Go github.com/minio/operator >=0 <7.1.0)

Commands are suggestions: review each one before running it.