Skip to main content
VulnerabilityPublished

CVE-2025-59531: argoproj argo-cd · Improper Check or Handling of Exceptional Conditions

Affects argoproj argo-cdSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in 2.14.20 : patch argoproj argo-cd soon.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.14.20
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately assess their Argo CD deployments for affected versions and upgrade to the fixed releases: 2.14.20, 3.2.0-rc2, 3.1.8, or 3.0.19 as appropriate. If immediate upgrade is not feasible, organizations should configure the webhook.bitbucketserver.secret to enforce proper authentication of incoming webhook payloads, which prevents the malformed payload from triggering the crash. Network-level protections such as restricting access to the /api/webhook endpoint using firewalls or API gateways can reduce exposure to unauthenticated requests. Implementing ingress controls and rate limiting can further mitigate the risk of DoS attacks. Monitoring Kubernetes logs and Argo CD API server health metrics for CrashLoopBackOff events or unusual webhook activity can provide early detection of exploitation attempts. Finally, organizations should review their incident response plans to include recovery procedures for Argo CD outages and consider isolating critical deployment pipelines to minimize blast radius.

Description

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.

References

Community reviews

Loading reviews…