A Single Kubernetes YAML Can Hand Over a GCP Organization, Exposing Users to Grave Security Risks
Google Cloud Platform (GCP) users have been left vulnerable to a potentially catastrophic security threat. The issue stems from the way some developers use Kubernetes YAML files to manage cloud resources, giving an attacker with limited access to the cluster the ability to take control of an entire organization.
When a developer creates a cloud resource in GCP, they typically need credentials to authenticate. However, this can become a problem when those credentials are scattered across machines, pipelines, and codebases – known as “secret sprawl.” To address this issue, developers have turned to GitOps operators, which use YAML configuration files to create or update cloud resources without requiring direct access to sensitive credentials.
Google’s Kubernetes Config Connector (KCC) is one such operator that watches for these configuration files and calls the corresponding GCP API on behalf of the developer. This means that developers never need to handle Google Cloud credentials themselves. However, this setup also creates a new problem: when an attacker has access to a Kubernetes namespace watched by KCC and permission to create IAMPolicyMember resources in that namespace, they can grant themselves any GCP IAM role that KCC’s service account is permitted to assign.
This technique, dubbed “ConfigConfusion,” was discovered by security researcher Justin O’Leary. In essence, an attacker can use a single Kubernetes YAML file to escalate their privileges and take control of the entire organization. The attack involves creating an IAMPolicyMember resource that grants themselves the role/owner or roles/resourcemanager.organizationAdmin, essentially handing over ownership of the organization.
The vulnerability is exacerbated by the fact that KCC’s service account often has broad permissions across multiple projects, folders, or even the entire organization. This makes it easy for an attacker to exploit and gain control of sensitive resources.
For users who rely on Kubernetes YAML files to manage their GCP resources, this vulnerability serves as a stark reminder of the importance of security best practices. Organizations must ensure that they are monitoring their clusters closely and implementing strict access controls to prevent such attacks from occurring.
To mitigate this risk, developers should be aware of the potential for ConfigConfusion and take steps to limit the permissions granted to KCC’s service account. This may involve creating a separate service account with more limited privileges or implementing additional authentication mechanisms.
As the cybersecurity landscape continues to evolve, it is essential that users remain vigilant and proactive in addressing emerging threats. By understanding the risks associated with Kubernetes YAML files and taking steps to secure their clusters, organizations can protect themselves against such attacks and maintain the integrity of their sensitive resources.
Source: Bleeping Computer — 2026-09-23