Unpatched Argo CD Repo-Server Flaw Poses Kubernetes Cluster Takeover Risk

A significant security vulnerability has been identified within Argo CD, a widely adopted tool for managing continuous delivery to Kubernetes clusters using GitOps principles. The flaw resides in Argo CD's repo-server component and allows for unauthenticated remote code execution (RCE) if an attacker can reach the component's internal network port. This means that an adversary could potentially gain control over the entire Kubernetes cluster where Argo CD is deployed. The vulnerability was discovered and reported by security firm Synacktiv in January 2025. However, as of July 2026, approximately eighteen months later, the issue remains unpatched, and no Common Vulnerabilities and Exposures (CVE) identifier has been assigned. This lack of official resolution led Synacktiv to publicly disclose the details to alert users to the potential risks. The attack chain abuses Argo CD's handling of Kustomize options, enabling a specially crafted request to pass attacker-controlled settings, such as `--enable-helm` and `--helm-command`. This manipulation can lead to the execution of code from a malicious Git repository on the repo-server host. Following successful code execution, researchers demonstrated the ability to steal environment variables like `REDIS_PASSWORD` and poison Argo CD's Redis-backed cache. This could force the deployment of attacker-controlled manifests during the next synchronization, ultimately leading to a full Kubernetes cluster compromise. Argo CD is designed to treat a Git repository as the single source of truth for application states, and the repo-server is crucial for pulling and rendering manifests. The concentration of cluster access and repository secrets within Argo CD's internal components makes such vulnerabilities particularly dangerous. This isn't the first time Argo CD has faced internal exposure issues; previous bugs in September 2025 (CVE-2025-55190) and May 2026 (CVE-2026-42880) also highlighted weaknesses in its internal security. Given the absence of a patch, the recommended defense is to implement robust network isolation. Users are advised to configure Kubernetes network policies to ensure that only Argo CD's own trusted components can access the repo-server and Redis ports. While Argo CD provides these policy files, installations via common Helm charts often leave them disabled by default. Administrators should verify that these policies are active to prevent a compromised pod within the cluster from reaching the repo-server and exploiting this critical flaw.