Security Digest · Vulnerability record
CVE-2025-55190: Argo CD's Project API Token Exposes Repository Credentials
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
CVSS 10.0 Critical EPSS 5.7% · p93
Should you act?
Critical, preconditions apply
Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 5.7%, percentile 93: FIRST’s model estimates a 5.7% chance of exploitation activity in the next 30 days, higher than 93% of all scored CVEs (elevated). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
github.com/argoproj/argo-cd/v2(Go) >= 2.13.0, < 2.13.9, fixed in 2.13.9;github.com/argoproj/argo-cd/v2(Go) >= 2.14.0, < 2.14.16, fixed in 2.14.16;github.com/argoproj/argo-cd/v3(Go) < 3.0.14, fixed in 3.0.14;github.com/argoproj/argo-cd/v3(Go) >= 3.1.0-rc1, < 3.1.2, fixed in 3.1.2. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
Summary Argo CD 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.
Component: Project API (/api/v1/projects/{project}/detailed)
Vulnerability Details Expected Behavior API tokens should require explicit permission to access sensitive credential information. Standard project permissions should not grant access to repository secrets. Actual Behavior API tokens with basic project permissions can retrieve all repository credentials associated with a project through the detailed project API endpoint.
Note: 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
Steps to Reproduce
Weakness type: CWE-200.
Product: github.com/argoproj/argo-cd/v2 (Go) · Assigned by: GitHub_M · Published: 2025-09-04
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/argoproj/argo-cd/v2 | >= 2.13.0, < 2.13.9 | 2.13.9 |
| Go | github.com/argoproj/argo-cd/v2 | >= 2.14.0, < 2.14.16 | 2.14.16 |
| Go | github.com/argoproj/argo-cd/v3 | < 3.0.14 | 3.0.14 |
| Go | github.com/argoproj/argo-cd/v3 | >= 3.1.0-rc1, < 3.1.2 | 3.1.2 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| argoproj | argo-cd | >= 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 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 10 Critical | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 5.66% probability of exploitation activity in the next 30 days; percentile 93.
Timeline
- — CVE record published by GitHub_M
- — GitHub-reviewed advisory GHSA-786q-9hcg-v9ff published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-786q-9hcg-v9ff github.com
- CVE.org record CVE-2025-55190 cve.org
- NVD entry CVE-2025-55190 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com