CVE-2025-55191 Repository Credentials Race Condition Crashes Argo CD Server
Attackers with repository permissions can trigger a race condition to crash the Argo CD server, causing denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-55191?
CVE-2025-55191 is a medium-severity vulnerability in Argoproj Argo Cd, published on 30 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-362
Which versions are affected by CVE-2025-55191?
12 open source packages ship an affected version, including github.com/argoproj/argo-cd/v3, argo-cd and github.com/argoproj/argo-cd. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/argoproj/argo-cd/v3 Go | From 3.0.0-rc1 | 3.0.19, 3.1.8, 3.2.0-rc2 |
github.com/argoproj/argo-cd/v3 Go | From 3.0.0-rc1 | 3.0.19 |
github.com/argoproj/argo-cd/v3 Go | From 3.0.0-rc1 | 3.0.19 |
github.com/argoproj/argo-cd/v3 Go | From 3.1.0-rc1 | 3.1.8 |
github.com/argoproj/argo-cd/v3 Go | From 3.1.0-rc1 | 3.1.8 |
github.com/argoproj/argo-cd/v3 Go | From 3.2.0-rc1 | 3.2.0-rc2 |
6 more packages
github.com/argoproj/argo-cd/v3 Go | From 3.2.0-rc1 | 3.2.0-rc2 |
argo-cd Bitnami | From 2.1.0 | 2.14.20, 3.0.19, 3.1.8 |
github.com/argoproj/argo-cd Go | All versions | None |
github.com/argoproj/argo-cd/v2 Go | From 2.1.0 | 2.14.20 |
github.com/argoproj/argo-cd/v2 Go | From 2.1.0 | 2.14.20 |
github.com/argoproj/argo-cd/v2 Go | From 2.1.0 | 2.14.20 |
Products include Argoproj Argo Cd.
How do I fix CVE-2025-55191?
Upgrade github.com/argoproj/argo-cd/v3 to a fixed version for your release line: 3.0.19, 3.1.8 or 3.2.0-rc2.
Is CVE-2025-55191 being exploited?
There is no known exploitation of CVE-2025-55191 in the wild and no public exploit code.
Other vulnerabilities in Argoproj Argo Cd
- CVE-2025-55190 Argo CD: Project API Token Exposes Repository Credentials
- CVE-2022-29165 Argo CD will blindly trust JWT claims if anonymous access is enabled
- CVE-2023-40029 Cluster secret might leak in cluster details page in Argo CD
- CVE-2022-24768 Improper access control allows admin privilege escalation in Argo CD
- CVE-2024-21652 Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
Sources
Also known as BIT-argo-cd-2025-55191, CLEANSTART-2026-WW74873, GHSA-g88p-r42r-ppp9, GO-2025-3994, MINI-79fx-pg7f-237j, MINI-7fmc-mxfv-p4v5 and 8 more.