argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links
argoproj argo-workflows
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows Go |
|
argoproj argo-workflows
| Product | Affected | Fixed in |
|---|---|---|
| github.com/argoproj/argo-workflows/v3 Go |
|
|
| github.com/argoproj/argo-workflows Go |
|
| No fix yet |
| github.com/argoproj/argo-workflows/v2 Go |
| No fix yet |
Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. Versions 3.6.13 and below and versions 3.7.0 through 3.7.4, contain unsafe untar code that handles symbolic links in archives. Concretely, the computation of a link's target and the subsequent check are flawed. An attacker can overwrite the file /var/run/argo/argoexec with a script of their choice, which would be executed at the pod's start. The patch deployed against CVE-2025-62156 is ineffective against malicious archives containing symbolic links. This issue is fixed in versions 3.6.14 and 3.7.5.
From the CVE record · GitHub_M
Argo Workflows has unsafe archive extraction code that mishandles symbolic links. An attacker who can supply a malicious archive can overwrite /var/run/argo/argoexec with a script that executes when the pod starts. The input does not specify whether authentication or other user interaction is required.
Teams running Argo Workflows 3.6.13 and below or 3.7.0–3.7.4, or using the Go packages github.com/argoproj/argo-workflows or github.com/argoproj/argo-workflows/v2, should check their deployments.