Skip to main content
CVE-2025-59537VulnerabilityPublished

CVE-2025-59537: argoproj argo-cd · Improper Input Validation

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, 08:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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

1. Upgrade Argo CD to the fixed versions: 2.14.20, 3.2.0-rc2, 3.1.8, or 3.0.19 as soon as possible to ensure the vulnerability is patched. 2. Configure webhook.gogs.secret to require authentication for incoming webhook events, preventing unauthenticated requests from reaching the /api/webhook endpoint. 3. Implement network-level controls such as firewall rules or API gateway filters to restrict access to the argocd-server API endpoints to trusted sources only. 4. Monitor Argo CD logs and Kubernetes cluster health for signs of unexpected crashes or webhook activity anomalies. 5. Conduct regular security assessments of CI/CD pipelines to identify and remediate input validation issues. 6. Educate DevOps teams about secure webhook configurations and the risks of default settings. 7. Consider deploying rate limiting on webhook endpoints to reduce the risk of DoS from malformed or excessive requests. 8. Maintain an inventory of Argo CD versions in use across the organization to prioritize patching efforts effectively.

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. With the default configuration, no webhook.gogs.secret set, Argo CD’s /api/webhook endpoint will crash the entire argocd-server process when it receives a Gogs push event whose JSON field commits[].repo is not set or is null. 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…