CVE-2025-55191
BaseFortify
Publication date: 2025-09-30
Last updated on: 2025-10-07
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| argoproj | argo_cd | From 2.1.0 (inc) to 2.14.20 (exc) |
| argoproj | argo_cd | From 3.0.0 (inc) to 3.0.19 (exc) |
| argoproj | argo_cd | From 3.1.0 (inc) to 3.1.8 (exc) |
| argoproj | argo_cd | 3.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a race condition in Argo CD's repository credentials handler that occurs when concurrent operations are performed on the same repository URL. It can cause the Argo CD server to panic and crash, leading to a denial-of-service condition. To exploit this, an attacker needs a valid API token with permissions to create, update, or delete repository resources.
How can this vulnerability impact me? :
The vulnerability can cause the entire Argo CD server to crash and become unavailable, disrupting all GitOps operations. Attackers can repeatedly trigger the race condition to maintain a denial-of-service state, impacting the availability of your continuous delivery processes.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately upgrade Argo CD to one of the fixed versions: 2.14.20, 3.2.0-rc2, 3.1.8, or 3.0.19. Additionally, restrict API tokens with repositories resource permissions (create, update, or delete actions) to trusted users only to reduce the risk of exploitation until the upgrade is applied.