Skip to content
Fencer Vulns
medium 6.5

CVE-2025-55191 json

Repository Credentials Race Condition Crashes Argo CD Server

published 2025-09-30 13 mo ago modified 2026-09-08 2 mo ago also BIT-argo-cd-2025-55191 , EUVD-2025-31768 , GHSA-g88p-r42r-ppp9 , GO-2025-3994

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.14.20
  • go github.com/argoproj/argo-cd/v3 3.0.19, 3.1.8, 3.2.0-rc2
  • bitnami argo-cd 2.14.20, 3.0.19, 3.1.8
  • linuxfoundation argo-cd 2.14.20, 3.0.19, 3.1.8, 3.2.0-rc2
  • linuxfoundation argo_continuous_delivery 2.14.20, 3.0.19, 3.1.8, 3.2.0-rc2
  • govulncheck-vulndb SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 0.0.20251023T162509-150000.1.110.1

suse advisories SUSE-SU-2025:3799-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20251023T162509-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2025:15666-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-55191 updated cvss 4.3

github.com/argoproj/argo-cd/v2: github.com/argoproj/argo-cd/v3: Argo CD race condition leading to crash

  • Red Hat Developer Hub 1 rhdh-orchestrator-dev-preview-beta/controller-rhel9-operator Red Hat OpenShift GitOps openshift-gitops-1/gitops-rhel8, openshift-gitops-1/argocd-agent-rhel8, openshift-gitops-1/gitops-rhel8-operator
    affected: workaround, no fix available “Systems may be configured to automatically restart a service upon crash and doing so may partially mitigate the availability impact of this vulnerability.”
  • Red Hat OpenShift GitOps 1.16 openshift-gitops-1
    fixed: vendor fix “Systems may be configured to automatically restart a service upon crash and doing so may partially mitigate the availability impact of this vulnerability.” RHSA-2025:17730
  • Red Hat OpenShift GitOps 1.17 openshift-gitops-1
    fixed: vendor fix “Systems may be configured to automatically restart a service upon crash and doing so may partially mitigate the availability impact of this vulnerability.” RHSA-2025:17731
  • Red Hat OpenShift GitOps 1.18 openshift-gitops-1
    fixed: vendor fix “Systems may be configured to automatically restart a service upon crash and doing so may partially mitigate the availability impact of this vulnerability.” RHSA-2025:18093
  • Red Hat OpenShift GitOps 1.16 openshift-gitops-1 Red Hat OpenShift GitOps 1.17 openshift-gitops-1 Red Hat OpenShift GitOps 1.18 openshift-gitops-1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
>=2.1.0, <2.14.20
2.14.20
go github.com/argoproj/argo-cd/v3
>=3.2.0-rc1, <3.2.0-rc2
>=3.1.0-rc1, <3.1.8
>=3.0.0-rc1, <3.0.19
3.2.0-rc2
3.1.8
3.0.19
bitnami argo-cd
>=2.1.0, <2.14.20
>=3.0.0, <3.0.19
>=3.1.0, <3.1.8
2.14.20
3.0.19
3.1.8
go github.com/argoproj/argo-cd
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.