CVE-2025-55190: Argo CD project API leaks repository credentials to low-privilege API tokens

Critical 9.9 EPSS 5.7%

Argo CD's project details endpoint (/api/v1/projects/{project}/detailed) returned repository usernames and passwords to any API token with project get permission, including tokens that only manage applications in a project and global grants such as 'p, role/user, projects, get, *, allow'. An attacker holding such a token can steal Git and Helm repository credentials. The Argo CD maintainers rate it critical (CVSS 9.9).

What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms

What to do now

  1. Check whether you run the affected software and which version (commands below).
  2. Install the fixed version for your system: see “Patch it” below.
  3. The Argo CD Deployments roll out new pods automatically. After upgrading, rotate repository credentials that tokens with project get permission could have read.
  4. If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.

Affected and fixed versions

Affected:

Fixed in:

Am I affected?

argocd version
kubectl -n argocd get deploy argocd-server -o jsonpath='{.spec.template.spec.containers[0].image}{"\n"}'

Patch it

Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.

Docker images
# Manifest installs (non-HA); use a fixed tag such as v3.1.2 (or a later release):
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.1.2/manifests/install.yaml
# HA installs:
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/v3.1.2/manifests/ha/install.yaml
# Helm (argo/argo-cd chart): upgrade the chart, or pin the image tag
helm repo update
helm upgrade argocd argo/argo-cd -n argocd --reuse-values --set global.image.tag=v3.1.2

General update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.

If you cannot patch yet

Sources

Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.