argoproj argo-cd up to 2.14.19/3.0.18/3.1.7/3.2.0-rc1 repository_secrets.go race condition

Summaryinfo

A vulnerability was found in argoproj argo-cd up to 2.14.19/3.0.18/3.1.7/3.2.0-rc1. It has been classified as problematic. Affected is an unknown function of the file util/db/repository_secrets.go. Performing a manipulation results in race condition. This vulnerability is reported as CVE-2025-55191. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as problematic has been found in argoproj argo-cd up to 2.14.19/3.0.18/3.1.7/3.2.0-rc1. This affects an unknown code block of the file util/db/repository_secrets.go. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently. This is going to have an impact on availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-55191 since 08/08/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.14.20, 3.0.19 or 3.1.8 eliminates this vulnerability. Applying the patch 701bc50d01c752cad96185f848088d287a97c7b7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• argoproj

Name

• argo-cd

Version

• 2.14.0
• 2.14.1
• 2.14.2
• 2.14.3
• 2.14.4
• 2.14.5
• 2.14.6
• 2.14.7
• 2.14.8
• 2.14.9
• 2.14.10
• 2.14.11
• 2.14.12
• 2.14.13
• 2.14.14
• 2.14.15
• 2.14.16
• 2.14.17
• 2.14.18
• 2.14.19
• 3.0.0
• 3.0.1
• 3.0.2
• 3.0.3
• 3.0.4
• 3.0.5
• 3.0.6
• 3.0.7
• 3.0.8
• 3.0.9
• 3.0.10
• 3.0.11
• 3.0.12
• 3.0.13
• 3.0.14
• 3.0.15
• 3.0.16
• 3.0.17
• 3.0.18
• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.2.0-rc1

License

• open-source

Website

• Product: https://github.com/argoproj/argo-cd/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion