Homepage

Improper Check or Handling of Exceptional Conditions Affecting argocd-fips-3.1 package, versions <3.1.8-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.06% (18th percentile)

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-MINIMOSLATEST-ARGOCDFIPS31-13330859
  • published6 Oct 2025
  • disclosed1 Oct 2025
Report a new vulnerability Found a mistake?

Introduced: 1 Oct 2025

NewCVE-2025-59531  (opens in a new tab)
CWE-703  (opens in a new tab)

How to fix?

Upgrade Minimos:latest argocd-fips-3.1 to version 3.1.8-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream argocd-fips-3.1 package and not the argocd-fips-3.1 package as distributed by Minimos. See How to fix? for Minimos:latest 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.