CVE-2025-55190
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-04

Last updated on: 2025-09-19

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-04
Last Modified
2025-09-19
Generated
2026-06-16
AI Q&A
2025-09-05
EPSS Evaluated
2026-06-15
NVD
CVE-2025-55190
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
argoproj argo_cd From 2.2.0 (inc) to 2.13.9 (exc)
argoproj argo_cd From 2.14.0 (inc) to 2.14.16 (exc)
argoproj argo_cd From 3.0.0 (inc) to 3.0.14 (exc)
argoproj argo_cd From 3.1.0 (inc) to 3.1.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-200 The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in Argo CD allows API tokens with project-level permissions, or any token with project get permissions, to retrieve sensitive repository credentials such as usernames and passwords through the project details API endpoint. This happens even if the token only has standard application management permissions and no explicit access to secrets. It affects multiple versions of Argo CD and is fixed in later versions.

Impact Analysis

The vulnerability can lead to unauthorized disclosure of sensitive repository credentials, which can compromise the security of your repositories and potentially allow attackers to gain further access or control over your Kubernetes deployments and infrastructure.

Mitigation Strategies

To mitigate this vulnerability, immediately upgrade Argo CD to one of the fixed versions: 2.13.9, 2.14.16, 3.0.14, or 3.1.2. Additionally, review and restrict API tokens with project get permissions to minimize exposure until the upgrade is applied.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-55190. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart