Repository Credentials Race Condition Crashes Argo CD Server

Summary

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Versions between 2.1.0 and 2.14.19, 3.2.0-rc1, 3.1.0-rc1 through 3.1.7, and 3.0.0-rc1 through 3.0.18 contain a race condition in the repository credentials handler that can cause the Argo CD server to panic and crash when concurrent operations are performed on the same repository URL. The vulnerability is located in numerous repository related handlers in the util/db/repository_secrets.go file. A valid API token with repositories resource permissions (create, update, or delete actions) is required to trigger the race condition. This vulnerability causes the entire Argo CD server to crash and become unavailable. Attackers can repeatedly and continuously trigger the race condition to maintain a denial-of-service state, disrupting all GitOps operations. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.

Timeline

1. Sep 30, 2025, 10:52 PM UTCCVE published
2. Oct 6, 2025, 6:32 PM UTCCISA SSVC assessment

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

3. Oct 6, 2025, 6:32 PM UTCRecord last updated

Affected versions

• argoproj argo-cd

  From 2.1.0 · fixed in 2.14.20; From 3.1.0-rc1 · fixed in 3.1.8; From 3.0.0-rc1 · fixed in 3.0.19

• github.com/argoproj/argo-cdGo

  All versions

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

  From 2.1.0 · fixed in 2.14.20

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

  From 3.0.0-rc1 · fixed in 3.0.19; From 3.1.0-rc1 · fixed in 3.1.8; From 3.2.0-rc1 · fixed in 3.2.0-rc2

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

  From 3.2.0-rc1 · fixed in 3.2.0-rc2

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

  From 3.1.0-rc1 · fixed in 3.1.8

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

  From 3.0.0-rc1 · fixed in 3.0.19

References 3