Database/Container, Kubernetes & orchestration

Argo Workflows (workflow executor, tar extraction symlink handling): The patch for CVE-2025-62156 missed symlinks, so a

CVE-2025-66626Container, Kubernetes & orchestrationGHSA-xrqc-7xgx-c9vhcurated

Impact

The patch for CVE-2025-62156 missed symlinks, so a crafted input artifact still escapes the extraction directory and writes anywhere the executor can reach. The executor container holds the workflow service account token and runs alongside the user's container, so an arbitrary write there converts a data-plane artifact into code execution inside Argo's own executor identity.

Who can reach it

Any user who can submit a workflow that consumes an attacker-supplied artifact, or who can plant an archive in a repository another tenant's workflow pulls from.

What to do

Upgrade to 3.6.14 or 3.7.5 and restart the controller so new pods get the fixed executor image. Do not stop at 3.6.12/3.7.3 - that is the incomplete fix for CVE-2025-62156.

References

https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xrqc-7xgx-c9vh https://nvd.nist.gov/vuln/detail/CVE-2025-66626

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.