Improper Validation of Array Index Affecting argo-workflows-3.6 package, versions *
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-MINIMOSLATEST-ARGOWORKFLOWS36-16242731
- published25 Apr 2026
- disclosed23 Apr 2026
Introduced: 23 Apr 2026
CVE-2026-40886 (opens in a new tab)How to fix?
There is no fixed version for Minimos:latest argo-workflows-3.6.
NVD Description
Note: Versions mentioned in the description apply only to the upstream argo-workflows-3.6 package and not the argo-workflows-3.6 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. From 3.6.5 to 4.0.4, an unchecked array index in the pod informer's podGCFromPod() function causes a controller-wide panic when a workflow pod carries a malformed workflows.argoproj.io/pod-gc-strategy annotation. Because the panic occurs inside an informer goroutine (outside the controller's recover() scope), it crashes the entire controller process. The poisoned pod persists across restarts, causing a crash loop that halts all workflow processing until the pod is manually deleted. This vulnerability is fixed in 4.0.5 and 3.7.14.