CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
Attackers with project-level API tokens can retrieve sensitive repository credentials via the project details endpoint, exposing secrets to unauthorized users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-55190?
CVE-2025-55190 is a critical vulnerability in Argoproj Argo Cd, published on 4 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2025-55190?
12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v2 Go | From 2.13.0 | 2.13.9, 2.14.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.13.0 | 2.13.9 |
github.com/argoproj/argo-cd/v2 Go | From 2.13.0 | 2.13.9 |
github.com/argoproj/argo-cd/v2 Go | From 2.14.0 | 2.14.16 |
github.com/argoproj/argo-cd/v2 Go | From 2.14.0 | 2.14.16 |
argo-cd Bitnami | From 2.13.0 | 2.13.9, 2.14.16, 3.0.14, 3.1.2 |
6 more packages
github.com/argoproj/argo-cd Go | All versions | None |
github.com/argoproj/argo-cd/v3 Go | All versions | 3.0.14, 3.1.2 |
github.com/argoproj/argo-cd/v3 Go | All versions | 3.0.14 |
github.com/argoproj/argo-cd/v3 Go | All versions | 3.0.14 |
github.com/argoproj/argo-cd/v3 Go | From 3.1.0-rc1 | 3.1.2 |
github.com/argoproj/argo-cd/v3 Go | From 3.1.0-rc1 | 3.1.2 |
Products include Argoproj Argo Cd.
How do I fix CVE-2025-55190?
Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.13.9 or 2.14.16.
Is CVE-2025-55190 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55190 exists.
Public exploit code: 1 Nuclei template.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
- CVE-2026-42880 ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction
Sources
Also known as BIT-argo-cd-2025-55190, CLEANSTART-2026-ES01541, GHSA-786q-9hcg-v9ff, GO-2025-3934, MINI-4x3m-4xfc-5jpp, MINI-6p6p-vxqg-hq5v and 6 more.