CVE-2025-55190: Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
Critical CVSS 9.9
- CVE id
- CVE-2025-55190
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Argo CD Runtimes and servers |
>= 2.2.0, < 2.13.9 >= 2.14.0, < 2.14.16 >= 3.0.0, < 3.0.14 >= 3.1.0, < 3.1.2 |
2.13.9, 2.14.16, 3.0.14, 3.1.2 |
How to fix it
Upgrade Argo CD to the fixed release of the line you run: 2.13.9, 2.14.16, 3.0.14, 3.1.2.
- Upgrade Argo CD (the quay.io/argoproj/argocd image, or the argo-cd Helm chart) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.