Argoproj argo-cd
Argo CD: Project API Token Exposes Repository Credentials
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. In versions 2.13.0 through 2.13.8, 2.14.0 through 2.14.15, 3.0.0 through 3.0.12 and 3.1.0-rc1 through 3.1.1, API tokens with project-level permissions are able to retrieve sensitive repository credentials (usernames, passwords) through the project details API endpoint, even when the token only has standard application management permissions and no explicit access to secrets. This vulnerability does not only affect project-level permissions. Any token with project get permissions is also vulnerable, including global permissions such as: `p, role/user, projects, get, *, allow`. This issue is fixed in versions 2.13.9, 2.14.16, 3.0.14 and 3.1.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.13.0, < 2.13.9
- >= 2.14.0, < 2.14.16
- >= 3.0.0, < 3.0.14
- >= 3.1.0-rc1, < 3.1.2
Fixed in 2.13.9, 2.14.16, 3.0.14, 3.1.2
Mitigation
Upgrade argo-cd to 2.13.9 or 2.14.16 or 3.0.14 or 3.1.2 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 13 days after publication; not in CISA KEV. First PoC: nuclei template: ArgoCD Project API Token Repository Credentials Exposure (nuclei template, 18 Sep 2025).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: ArgoCD Project API Token Repository Credentials Exposure | 18 Sep 2025 | 14 Nov 2026 |