CVE-2025-55190: Argo CD API Token Vulnerability Exposes Sensitive Repository Credentials
Summary
CVE-2025-55190: Argo CD's Project API Token Exposes Repository Credentials. Affects github.com/argoproj/argo-cd/v2 across 2 version ranges.
>= 2.13.0, < 2.13.9
>= 2.14.0, < 2.14.16
Fixed in 2.13.9 or 2.14.16, depending on the release line you run. How to fix ↓
Also tracked for
- argo-cd · Bitnami
- github.com/argoproj/argo-cd · Go
The same CVE-2025-55190 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It enables users to manage applications and their deployment configurations through Git repositories. The tool provides features such as application synchronization, health monitoring, and rollback capabilities. However, a critical vulnerability has been identified in its Project API, which allows API tokens with project-level permissions to access sensitive repository credentials, posing a significant security risk.
Vulnerability Detail
The vulnerability arises from the Project API's insufficient permission checks, allowing API tokens with basic project permissions to retrieve sensitive repository credentials, including usernames and passwords. This issue can lead to unauthorized access to sensitive information, potentially compromising the security of the applications managed by Argo CD. The vulnerability affects any token with project get permissions, including those with global permissions, making it a widespread concern.
How To Fix
Latest published version: v2.14.21 as of 22 Oct 2026
go get github.com/argoproj/argo-cd/v2@v2.14.21Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
>= 2.13.0, < 2.13.92.13.9go get github.com/argoproj/argo-cd/v2@v2.13.9 -
>= 2.14.0, < 2.14.162.14.16go get github.com/argoproj/argo-cd/v2@v2.14.16
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, restrict API tokens to only have the necessary permissions and avoid granting project get permissions to tokens that do not require access to sensitive repository credentials. Review and audit existing tokens to ensure they adhere to the principle of least privilege.
Conclusion
The CVE-2025-55190 vulnerability in Argo CD poses a significant risk by allowing unauthorized access to sensitive repository credentials. It is crucial for users to update to the patched versions or implement workarounds to mitigate the risk. Regular audits of API token permissions are also recommended to enhance security.
See every vulnerability recorded for github.com/argoproj/argo-cd/v2 →
FAQ
CVE-2025-55190 is a critical vulnerability in Argo CD that allows API tokens with project-level permissions to access sensitive repository credentials.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
The vulnerability can lead to unauthorized access to sensitive repository credentials, which may compromise the security of applications managed by Argo CD.
You can update to a patched version by using the command go get github.com/argoproj/argo-cd/v2@v2.13.9 or go get github.com/argoproj/argo-cd/v3@v3.0.14.
If you cannot update immediately, review and restrict API token permissions to limit access to sensitive information as a temporary measure.
References
Related vulnerabilities
Recent vulnerabilities recorded for github.com/argoproj/argo-cd/v2.
