Improper Check or Handling of Exceptional Conditions Affecting argo-cd-2.13 package, versions <2.13.9-r5
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-ARGOCD213-15989943
- published12 Apr 2026
- disclosed1 Oct 2025
Introduced: 1 Oct 2025
CVE-2025-59531 (opens in a new tab)How to fix?
Upgrade Chainguard argo-cd-2.13 to version 2.13.9-r5 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream argo-cd-2.13 package and not the argo-cd-2.13 package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.