GPU VulnDB

Database/Container, Kubernetes & orchestration

Argo CD: any token with project get permission can read repository credentials

CVSS 9.9CVE-2025-55190Container, Kubernetes & orchestrationcurated

Impact

An API token that only has standard application-management rights can read the usernames and passwords stored for Git and Helm repositories through the project details endpoint, including tokens holding only a global projects, get grant. On a GPU fleet where Argo CD is the GitOps controller for the whole cluster, those credentials are usually write-capable against the manifest repositories that define node pools, device-plugin DaemonSets, admission policy and inference deployments. An attacker who harvests them can push manifests that schedule privileged pods onto GPU nodes, so a low-privilege automation token converts into cluster-wide control without ever touching a Kubernetes Secret. Any team or tenant that was given a scoped Argo CD token is in the blast radius.

Who can reach it

Authenticated holder of any Argo CD API token with project get permission - a CI job token or a tenant-scoped automation account is enough. No access to Kubernetes Secrets and no admin role required; reachable wherever the Argo CD API is exposed.

What to do

Upgrade Argo CD to 2.13.9, 2.14.16, 3.0.14 or 3.1.2 and restart the argocd-server deployment - a control-plane component restart, no node drain or reboot. Because credentials may already have been read, rotate every repository credential and audit project get grants on existing tokens after patching.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.