Homepage

Uncaught Exception Affecting argocd-fips-3.1-compat package, versions <3.1.8-r0

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.05% (17th 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 Learn

Learn about Uncaught Exception vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-MINIMOSLATEST-ARGOCDFIPS31COMPAT-13320189
  • published6 Oct 2025
  • disclosed1 Oct 2025
Report a new vulnerability Found a mistake?

Introduced: 1 Oct 2025

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

How to fix?

Upgrade Minimos:latest argocd-fips-3.1-compat 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-compat package and not the argocd-fips-3.1-compat 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. 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.