Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 2 September 2026.
- Which products and versions are affected?
- Google GKE Multi-Cloud Prior to patch date 2026-09-02.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a web application.
- Am I affected?
- Check whether you run Google GKE Multi-Cloud or Google Cloud Platform at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass in GKE Multi-Cloud's CreateAttachedCluster, CreateAwsCluster, and CreateAzureCluster APIs due to missing project-level permission validation. An attacker with network access to these APIs could register a cluster into an arbitrary target project's Workload Identity Federation without checking whether they have permission to modify that project. Successful exploitation allows creation of Workload Identity tokens and impersonation of Kubernetes Service Accounts bound in the target project, effectively granting the attacker the privileges of those service accounts. The vulnerability requires authentication but does not require explicit target project membership. Full details and remediation guidance are available in the GKE security bulletin linked in the advisory.
Affected products
- Google GKE Multi-Cloud Prior to patch date 2026-09-02
Timeline
- 2026-09-02: disclosed