Cluster information disclosure via impersonable ServiceAccount
Published Jun 24, 2025 · Updated May 26, 2026
Incorrect privilege assignment in NVIDIA AIS K8s Operator before 2.3.0 allows remote authenticated users to disclose cluster data. The operator creates a namespaced ServiceAccount bound to a cluster-wide ClusterRole, allowing that account to be impersonated for elevated access. Exploitation requires existing Kubernetes privileges sufficient to create an AIS custom resource and use the attached ServiceAccount; the reported consequence is information disclosure.
Summary
What happened
Incorrect privilege assignment in NVIDIA AIS K8s Operator before 2.3.0 allows remote authenticated users to disclose cluster data. The operator creates a namespaced ServiceAccount bound to a cluster-wide ClusterRole, allowing that account to be impersonated for elevated access. Exploitation requires existing Kubernetes privileges sufficient to create an AIS custom resource and use the attached ServiceAccount; the reported consequence is information disclosure.
The record
- CVE
- CVE-2025-23260
- Published
- Jun 24, 2025
- Updated
- May 26, 2026
- Vendor
- DPDK Project
- Product
- AIS K8s Operator
- Classifications
- CWE-266, T1078.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2025CVE publishedPublication date reported by the CVE source.
- May 26, 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=All versions prior 2.3.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