Argo CD: Project API Token Exposes Repository Credentials

Summary

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.

Timeline

1. Sep 4, 2025, 10:37 PM UTCCVE published
2. Sep 5, 2025, 4:07 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: total

3. Sep 5, 2025, 4:07 PM UTCRecord last updated

Affected versions

• argoproj argo-cd

  From 2.13.0 · fixed in 2.13.9; From 2.14.0 · fixed in 2.14.16; From 3.0.0 · fixed in 3.0.14; From 3.1.0-rc1 · fixed in 3.1.2

• github.com/argoproj/argo-cd/v2Go

  From 2.13.0 · fixed in 2.13.9

• github.com/argoproj/argo-cd/v2Go

  From 2.14.0 · fixed in 2.14.16

• github.com/argoproj/argo-cd/v3Go

  fixed in 3.0.14

• github.com/argoproj/argo-cd/v3Go

  From 3.1.0-rc1 · fixed in 3.1.2

• github.com/argoproj/argo-cdGo

  All versions

• github.com/argoproj/argo-cd/v2Go

  From 2.13.0 · fixed in 2.13.9; From 2.14.0 · fixed in 2.14.16

• github.com/argoproj/argo-cd/v3Go

  fixed in 3.0.14; From 3.1.0-rc1 · fixed in 3.1.2

References 3