argoproj argo-cd up to 3.2.0-rc1 /api/webhook repository.links.clone improper check or handling of exceptional conditions

Summaryinfo

A vulnerability, which was classified as problematic, has been found in argoproj argo-cd up to 1.8.7/2.14.19/3.0.18/3.1.7/3.2.0-rc1. This affects an unknown part of the file /api/webhook. Performing a manipulation of the argument repository.links.clone results in improper check or handling of exceptional conditions. This vulnerability is identified as CVE-2025-59531. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in argoproj argo-cd up to 1.8.7/2.14.19/3.0.18/3.1.7/3.2.0-rc1. This affects an unknown functionality of the file /api/webhook. The manipulation of the argument repository.links.clone with an unknown input leads to a improper check or handling of exceptional conditions vulnerability. CWE is classifying the issue as CWE-703. The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. 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 1.2.0 through 1.8.7, 2.0.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.7 and 3.0.18 are vulnerable to malicious API requests which can crash the API server and cause denial of service to legitimate clients. Without a configured webhook.bitbucketserver.secret, Argo CD's /api/webhook endpoint crashes when receiving a malformed Bitbucket Server payload (non-array repository.links.clone field). A single unauthenticated request triggers CrashLoopBackOff, and targeting all replicas causes complete API outage. This issue is fixed in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-59531 since 09/17/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2.14.20, 3.0.19, 3.1.8 or 3.2.0-rc2 eliminates this vulnerability. Applying the patch 5c466a4e39802e059e75c0008ae7b7b8e842538f 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.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2251). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• Red Hat Enterprise Linux
• Red Hat OpenShift GitOps

Productinfo

Vendor

• argoproj

Name

• argo-cd

Version

• 1.8.0
• 1.8.1
• 1.8.2
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.8.7
• 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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion