argoproj argo-cd up to 2.13.8/2.14.15/3.0.13/3.1.1 API Endpoint role/user information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in argoproj argo-cd up to 2.13.8/2.14.15/3.0.13/3.1.1. This issue affects some unknown processing of the file role/user of the component API Endpoint. This manipulation causes information disclosure. This vulnerability is handled as CVE-2025-55190. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in argoproj argo-cd up to 2.13.8/2.14.15/3.0.13/3.1.1. It has been declared as problematic. Affected by this vulnerability is an unknown code of the file role/user of the component API Endpoint. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE 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.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-55190 since 08/08/2025. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 2.13.9, 2.14.16, 3.0.14 or 3.1.2 eliminates this vulnerability. Applying the patch e8f86101f5378662ae6151ce5c3a76e9141900e8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-1978). Be aware that VulDB is the high quality source for vulnerability data.
Affected
- Red Hat OpenShift
Product
Vendor
Name
Version
- 2.13.0
- 2.13.1
- 2.13.2
- 2.13.3
- 2.13.4
- 2.13.5
- 2.13.6
- 2.13.7
- 2.13.8
- 2.14.0
- 2.14.1
- 2.14.2
- 2.14.3
- 2.14.4
- 2.14.5
- 2.14.6
- 2.14.7
- 2.14.8
- 2.14.9
- 2.14.10
- 2.14.11
- 2.14.12
- 2.14.13
- 2.14.14
- 2.14.15
- 3.0.0
- 3.0.1
- 3.0.2
- 3.0.3
- 3.0.4
- 3.0.5
- 3.0.6
- 3.0.7
- 3.0.8
- 3.0.9
- 3.0.10
- 3.0.11
- 3.0.12
- 3.0.13
- 3.1.0
- 3.1.1
License
Website
- Product: https://github.com/argoproj/argo-cd/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.9
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: argo-cd 2.13.9/2.14.16/3.0.14/3.1.2
Patch: e8f86101f5378662ae6151ce5c3a76e9141900e8
Timeline
08/08/2025 CVE reserved09/05/2025 Advisory disclosed
09/05/2025 VulDB entry created
09/05/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-786q-9hcg-v9ff
Status: Confirmed
CVE: CVE-2025-55190 (🔒)
GCVE (CVE): GCVE-0-2025-55190
GCVE (VulDB): GCVE-100-322711
CERT Bund: WID-SEC-2025-1978 - Red Hat OpenShift GitOps (Argo CD): Schwachstelle ermöglicht Offenlegung von Informationen
Entry
Created: 09/05/2025 07:40Updated: 09/05/2025 12:00
Changes: 09/05/2025 07:40 (68), 09/05/2025 12:00 (7)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.