STS credential access via audience-unscoped TokenReview
Published Apr 22, 2025 · Updated Jan 23, 2026
Authentication flaw in MinIO Operator before 7.1.0 allows remote attackers to obtain STS credentials with a replayed service-account token. The STS TokenReview request omits spec.audiences, so Kubernetes defaults validation to the API-server audience instead of sts.min.io. Exploitation requires a valid Kubernetes service-account token whose account has a PolicyBinding, and successful replay grants temporary access to the bound MinIO tenant.
Summary
What happened
Authentication flaw in MinIO Operator before 7.1.0 allows remote attackers to obtain STS credentials with a replayed service-account token. The STS TokenReview request omits spec.audiences, so Kubernetes defaults validation to the API-server audience instead of sts.min.io. Exploitation requires a valid Kubernetes service-account token whose account has a PolicyBinding, and successful replay grants temporary access to the bound MinIO tenant.
The record
- CVE
- CVE-2025-32963
- Published
- Apr 22, 2025
- Updated
- Jan 23, 2026
- Vendor
- MinIO
- Product
- MinIO Operator
- Classifications
- CWE-522, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2025CVE publishedPublication date reported by the CVE source.
- Jan 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 7.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo