CVE-2025-55190
published 2025-09-04CVE-2025-55190: 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…
PriorityP183critical9.9CVSS 3.1
AVNACLPRLUINSCCHIHAH
ITWEXPLOITVulnCheck KEV
Exploited in the wild
EPSS
5.34%
92.0th percentile
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
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo-cd | — | — |
| argoproj | argo_cd | >= 2.14.0 < 2.14.16 | 2.14.16 |
| argoproj | argo_cd | >= 2.2.0 < 2.13.9 | 2.13.9 |
| argoproj | argo_cd | >= 3.0.0 < 3.0.14 | 3.0.14 |
| argoproj | argo_cd | >= 3.1.0 < 3.1.2 | 3.1.2 |
| github.com | argoproj_argo-cd_v2 | >= 2.13.0 < 2.13.9 | 2.13.9 |
| github.com | argoproj_argo-cd_v2 | >= 2.14.0 < 2.14.16 | 2.14.16 |
| github.com | argoproj_argo-cd_v3 | >= 0 < 3.0.14 | 3.0.14 |
| github.com | argoproj_argo-cd_v3 | >= 3.1.0-rc1 < 3.1.2 | 3.1.2 |
Detection & IOCsextracted from sources · hover to see the quote
yara↗
strings: $a = '"repositories":' $b = '"username":' $c = '"password":' condition: all of them
- →Monitor for GET requests to the /api/v1/projects/{project}/detailed endpoint, especially from API tokens with only basic project-get permissions. A successful exploit returns HTTP 200 with a body containing 'repositories', 'username', and 'password' fields. ↗
- →Flag API tokens bearing global permissions of the form `p, role/user, projects, get, *, allow` accessing the project details endpoint, as these are explicitly called out as vulnerable. ↗
- →A two-step HTTP sequence is the exploit pattern: first a POST to /api/v1/session to obtain a token, then a GET to /api/v1/projects/default/detailed using that token. Correlate these two requests from the same source IP. ↗
- →Inspect HTTP 200 responses from /api/v1/projects/*/detailed for JSON bodies containing both 'username' and 'password' keys nested inside a 'repositories' array — this indicates successful credential exfiltration. ↗
- ·Exploitation requires a valid Argo CD API token; the vulnerability is not exploitable by unauthenticated users. ↗
- ·The Nuclei detection template requires valid ArgoCD credentials (username/password) to be supplied as variables before it can test the vulnerability. ↗
- ·The vulnerability scope is not limited to project-level tokens; any token with project get permissions — including broad global roles — is affected. ↗
- ·Red Hat notes that exploitation does not grant full system control; attackers can only access/tamper with projects associated with the compromised API token. ↗
CVSS provenance
nvdv3.19.9CRITICALCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vulncheck9.9CRITICAL
vendor_redhat9.9CRITICAL
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Argo CD's Project API Token Exposes Repository Credentials in github.com/argoproj/argo-cd
osv·2025-09-08
CVE-2025-55190 Argo CD's Project API Token Exposes Repository Credentials in github.com/argoproj/argo-cd
Argo CD's Project API Token Exposes Repository Credentials in github.com/argoproj/argo-cd
Argo CD's Project API Token Exposes Repository Credentials in github.com/argoproj/argo-cd
GHSA
Argo CD's Project API Token Exposes Repository Credentials
ghsa·2025-09-04
CVE-2025-55190 [CRITICAL] CWE-200 Argo CD's Project API Token Exposes Repository Credentials
Argo CD's Project API Token Exposes Repository Credentials
### 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.
OSV
Argo CD's Project API Token Exposes Repository Credentials
osv·2025-09-04
CVE-2025-55190 [CRITICAL] Argo CD's Project API Token Exposes Repository Credentials
Argo CD's Project API Token Exposes Repository Credentials
### 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.
VulnCheck
argoproj argo_cd Exposure of Sensitive Information to an Unauthorized Actor
vulncheck·2025·CVSS 9.9
CVE-2025-55190 [CRITICAL] argoproj argo_cd Exposure of Sensitive Information to an Unauthorized Actor
argoproj argo_cd Exposure of Sensitive Information to an Unauthorized Actor
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.
Red Hat
github.com/argoproj/argo-cd: Project API Token Exposes Repository Credentials
vendor_redhat·2025-09-04·CVSS 9.9
CVE-2025-55190 [CRITICAL] CWE-522 github.com/argoproj/argo-cd: Project API Token Exposes Repository Credentials
github.com/argoproj/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.
No detection rules found.
Nuclei
ArgoCD Project API Token Repository Credentials Exposure
nuclei·CVSS 9.9
CVE-2025-55190 [CRITICAL] ArgoCD Project API Token Repository Credentials Exposure
ArgoCD Project API Token Repository Credentials Exposure
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. This vulnerability affects versions
v2.2.0-rc1 and later, including 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. Any token with project get permissions is vulnerable, including global permissions.
Note: This template requires valid ArgoCD credentials (username/password) to test the vulnerability.
Template:
id: CVE-2025-55190
info:
name: ArgoCD Project API Token Repository Credentials Exposure
author: nukun
Hackernews
Unpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters
blogs_hackernews·2026-07-02
CVE-2024-31989 Unpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters
Home
Threat Intelligence
Vulnerabilities
Cyber Attacks
Webinars
Expert Insights
Awards
Webinars
Awards
Free eBooks
About THN
Jobs
Advertise with us
## Unpatched Argo CD Repo-Server Flaw Could Let Attackers Take Over Kubernetes Clusters
Argo CD , a widely used tool for deploying software to Kubernetes, has an unpatched flaw in its repo-server component that lets an unauthenticated attacker run code, provided they can reach the component's internal network port.
Synacktiv , which found the bug, says it can lead to a full cluster takeover. There is no fix and no CVE. The firm says it reported the flaw to Argo CD's maintainers in January 2025; roughly eighteen months later, it remains unpatched, so it published the details to warn users.
The bug sits in repo-server, the Argo
Bleepingcomputer
Max severity Argo CD API flaw leaks repository credentials
blogs_bleepingcomputer·2025-09-05·CVSS 9.9
CVE-2025-55190 [CRITICAL] Max severity Argo CD API flaw leaks repository credentials
## Max severity Argo CD API flaw leaks repository credentials
## Bill Toulas
An Argo CD vulnerability allows API tokens with even low project-level get permissions to access API endpoints and retrieve all repository credentials associated with the project.
The flaw, tracked under CVE-2025-55190 , is rated with the maximum severity score of 10.0 in CVSS v3, and allows bypassing isolation mechanisms used to protect sensitive credential information.
Attackers holding those credentials could then use them to clone private codebases, inject malicious manifests, attempt downstream compromise, or pivot to other resources where the same credentials are reused.
Argo CD is a Kubernetes-native continuous deployment (CD) and GitOps tool used by numerous organizations, including large enterprises
2025-09-04
Published
Exploited in the wild