Argo Workflows (workflow executor, artifact unpack path handling): Archive entries with traversal paths escape the

Impact

Archive entries with traversal paths escape the temporary unpack directory during artifact extraction, letting a crafted archive overwrite files outside it - including paths under /etc in the executor. Because the executor carries the workflow's Kubernetes identity, a poisoned input artifact turns into control over a component that other tenants' workflows also run through.

Who can reach it

Any user able to submit a workflow that pulls an attacker-controlled input artifact, or able to write into a shared artifact repository path.

What to do

Upgrade to 3.6.12 or 3.7.3, then immediately to 3.6.14 / 3.7.5 because the initial fix was bypassable via symlinks (CVE-2025-66626). Restart the controller so new workflow pods pick up the corrected executor.

References

Related entries

• Argo Workflows (workflow executor, tar extraction symlink handling): The patch for CVE-2025-62156 missed symlinks, so aCVE-2025-66626 · Argo Workflows (workflow executor, tar extraction symlink handling)High
• Podman: kube play follows symlinks in Secret/ConfigMap volumes and overwrites host filesCVE-2025-9566 · Podman (podman kube play, Secret/ConfigMap volume mounts)High
• Moby: plugin privilege approval can be bypassed during docker plugin installCVE-2026-33997 · Moby / Docker Engine daemon (docker plugin install privilege comparison)High
• Argo Workflows (controller, hostNetwork / securityContext / serviceAccountName merge path): The first fix forCVE-2026-42296 · Argo Workflows (controller, hostNetwork / securityContext / serviceAccountName merge path)High
• containerd: On SELinux hosts, an unprivileged pod with a hostPath volume can gain full read/write to the host filesystemCVE-2021-43816 · containerdHigh
• Cilium: IPsec transparent encryption is cryptographically ineffectiveCVE-2024-28860 · CiliumHigh