Argo CD 2025 API Flaw Exposes Repository Credentials: What Enterprises Must Know
In September 2025, a critical vulnerability (CVE-2025-55190) in Argo CD—a widely used Kubernetes-native continuous deployment platform—was discovered that allowed API tokens, including those with minimal project-level permissions, to access API endpoints and retrieve all repository credentials for a given project. While the flaw required possession of a valid Argo CD API token, even low-privileged users could exploit this issue to bypass established isolation mechanisms and exfiltrate sensitive repository usernames and passwords. This exposure could enable attackers to clone proprietary codebases, inject malicious configurations, and potentially initiate supply chain compromises or further lateral movement, particularly impactful given Argo CD's widespread enterprise adoption by organizations like Adobe, Google, IBM, and Capital One. The incident underscores the ongoing risks posed by misconfigured API permissions in CI/CD pipelines, particularly as attackers increasingly target software supply chains. With credential-based attacks on the rise and major regulatory and industry scrutiny on API security, organizations must act quickly to patch, enhance access controls, and apply zero-trust principles in DevOps contexts.
Kill Chain









