CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5) in argoproj argo cd. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/argoproj/argo-cd/v2 2.14.20.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hgithub.com/argoproj/argo-cd/v2 (Go): fixed in 2.14.20github.com/argoproj/argo-cd/v3 (Go): fixed in 3.2.0-rc2, 3.1.8, 3.0.19Explain CVE-2025-59531 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-59531?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-59531?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-59531 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| argoproj:argo_cd | from 1.2.0 through 1.8.7 |
| argoproj:argo_cd | from 2.0.0 before 2.14.20 |
| argoproj:argo_cd | from 3.0.0 before 3.0.19 |
| argoproj:argo_cd | from 3.1.0 before 3.1.8 |
| argoproj:argo_cd | 3.2.0:rc1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-f9gq-prrc-hrhc | Go | github.com/argoproj/argo-cd | >=1.2.0 <=1.8.7 | no fix published |
| GHSA-f9gq-prrc-hrhc | Go | github.com/argoproj/argo-cd/v2 | >=2.0.0-rc1 <2.14.20 | 2.14.20 |
| GHSA-f9gq-prrc-hrhc | Go | github.com/argoproj/argo-cd/v3 | >=3.2.0-rc1 <3.2.0-rc2 | 3.2.0-rc2 |
| GHSA-f9gq-prrc-hrhc | Go | github.com/argoproj/argo-cd/v3 | >=3.1.0-rc1 <3.1.8 | 3.1.8 |
| GHSA-f9gq-prrc-hrhc | Go | github.com/argoproj/argo-cd/v3 | >=3.0.0-rc1 <3.0.19 | 3.0.19 |
| GO-2025-3993 | Go | github.com/argoproj/argo-cd | >=1.2.0 | no fix published |
| GO-2025-3993 | Go | github.com/argoproj/argo-cd/v2 | <2.14.20 | 2.14.20 |
| GO-2025-3993 | Go | github.com/argoproj/argo-cd/v3 | >=3.0.0-rc1 <3.0.19 >=3.1.0-rc1 <3.1.8 >=3.2.0-rc1 <3.2.0-rc2 | 3.0.19, 3.1.8, 3.2.0-rc2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | 0.0.20251023T162509-150000.1.110.1 | SUSE-SU-2025:3799-1 |
| openSUSE | Leap 15.6 | govulncheck-vulndb | 0.0.20251023T162509-150000.1.110.1 | SUSE-SU-2025:3799-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-SU-2026:21483-1 |
| openSUSE | Tumbleweed | govulncheck-vulndb | 0.0.20251023T162509-1.1 | openSUSE-SU-2025:15666-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Important.
This vulnerability was rated as Important by the Red Hat Product Security team, this happens because an unauthenticated attacker is able to cause a denial of service from the whole GitOps cluster. This vulnerability affects only clusters without a configured 'webhook.bitbucket.secret' configuration key, thus clusters that have this option configured are not exposed to this flaw.
This vulnerability lies in a unsafe cast when trying to retrieve the `repository.links.clone`JSON field from BitBucket-Server push request. When the unsafe cast is triggered, the goroutine created by the worker to process the request will fail within an assertion panic and, as it lacks a recovery routine, the whole argocd-server binary will be terminated. If an attacker manages to force all the argocd-server replica nodes to reach this assertion failure, a Denial of Service of the whole cluster will happen.
If a BitBucket repository is being used by GitOps it's possible to mitigate this vulnerability by setting up a BitBucket webhook secret to ensure only trusted parties can access the webhook endpoint.
In case BitBucket is not being used, the user can set the webhook secret to a long random value to prevent the webhook from being called:
~~~
apiVersion: v1
kind: Secret
metadata:
name: argocd-secret
type: Opaque
data:
+ webhook.bitbucketserver.secret: <your base64-encoded secret here>
~~~
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/argocd-rhel8:1.16 | Fixed 2025-10-09 | RHSA-2025:17730 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/argocd-rhel9:1.16 | Fixed 2025-10-09 | RHSA-2025:17730 |
| Red Hat OpenShift GitOps 1.16 | openshift-gitops-1/gitops-operator-bundle:1.16 | Fixed 2025-10-09 | RHSA-2025:17730 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/argocd-rhel8:1.17 | Fixed 2025-10-09 | RHSA-2025:17731 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/argocd-rhel9:1.17 | Fixed 2025-10-09 | RHSA-2025:17731 |
| Red Hat OpenShift GitOps 1.17 | openshift-gitops-1/gitops-operator-bundle:1.17 | Fixed 2025-10-09 | RHSA-2025:17731 |
| Red Hat OpenShift GitOps 1.18 | openshift-gitops-1/argocd-rhel8:1.18 | Fixed 2025-10-15 | RHSA-2025:18093 |
| Red Hat OpenShift GitOps 1.18 | openshift-gitops-1/argocd-rhel9:1.18 | Fixed 2025-10-15 | RHSA-2025:18093 |
| Red Hat OpenShift GitOps 1.18 | openshift-gitops-1/gitops-operator-bundle:1.18 | Fixed 2025-10-15 | RHSA-2025:18093 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-59531.