CVE-2025-59538: argoproj argo-cd · Uncaught Exception
Affects argoproj argo-cdSource CVE Database V5
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
- EPSS
- 9.3% chance of exploitation in 30 days – higher than 95% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 upgrade affected Argo CD instances to the fixed versions: 2.14.20, 3.2.0-rc2, 3.1.8, or 3.0.19, depending on their current version. If immediate upgrade is not feasible, ensure that webhook.azuredevops.username and webhook.azuredevops.password are properly set in the configuration to prevent the vulnerable code path from being triggered. Implement network-level access controls to restrict inbound traffic to the /api/webhook endpoint, limiting exposure to trusted sources only. Monitor argocd-server logs for unexpected crashes or webhook payload anomalies, and consider deploying runtime protection or crash recovery mechanisms to minimize downtime. Conduct security reviews of webhook integrations and validate incoming payloads at the ingress level to detect malformed or suspicious requests. Finally, incorporate this vulnerability into incident response and patch management workflows to ensure timely remediation.
Description
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. For versions 2.9.0-rc1 through 2.14.19, 3.0.0-rc1 through 3.2.0-rc1, 3.1.6 and 3.0.17, when the webhook.azuredevops.username and webhook.azuredevops.password are not set in the default configuration, the /api/webhook endpoint crashes the entire argocd-server process when it receives an Azure DevOps Push event whose JSON array resource.refUpdates is empty. The slice index [0] is accessed without a length check, causing an index-out-of-range panic. A single unauthenticated HTTP POST is enough to kill the process. This issue is resolved in versions 2.14.20, 3.2.0-rc2, 3.1.8 and 3.0.19.