HighGHSA-xrqc-7xgx-c9vhBIT-argo-workflows-2025-66626CVE-2025-66626GO-2025-4223

RCE via ZipSlip and symbolic links in argoproj/argo-workflows

Published 9 Dec 2025 · Updated 10 Sept 2026

Is your project on an affected github.com/argoproj/argo-workflows/v3?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=3.7.0 <3.7.5
Fixed in
3.7.5
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.7.5
Affected
<3.6.14
Fixed in
3.6.14
Update to the fixed version for your release line, for example:go get github.com/argoproj/argo-workflows/v3@v3.6.14
Affected
<=2.5.3-rc4
Fixed in
No fix released

Details

Summary

The patch deployed against CVE-2025-62156 is ineffective against malicious archives containing symbolic links.

Details

The untar code that handles symbolic links in archives is unsafe. Concretely, the computation of the link's target and the subsequent check are flawed: https://github.com/argoproj/argo-workflows/blob/5291e0b01f94ba864f96f795bb500f2cfc5ad799/workflow/executor/executor.go#L1034-L1037

PoC

1. Create a malicious archive containing two files: a symbolik link with path "./work/foo" and target "/etc", and a normal text file with path "./work/foo/hostname". 2. Deploy a workflow like the one in https://github.com/argoproj/argo-workflows/security/advisories/GHSA-p84v-gxvw-73pf with the malicious archive mounted at /work/tmp. 3. Submit the workflow and wait for its execution. 4. Connect to the corresponding pod and observe that the file "/etc/hostname" was altered by the untar operation performed on the malicious archive. The attacker can hence alter arbitrary files in this way.

Impact

The attacker can overwrite the file /var/run/argo/argoexec with a script of their choice, which will be executed at the pod's start.

Is GHSA-xrqc-7xgx-c9vh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/argoproj/argo-workflows/v3, and gives you the command that fixes it.

More advisories for github.com/argoproj/argo-workflows/v3

  • LowCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) in github.com/argoproj/argo-workflows · 18 Aug 2026
  • HighCVE-2026-54526Argo Workflows: ArtifactGC.PodSpecPatch bypasses Strict/Secure template reference allow-list (Incomplete fix for CVE-2026-31892) · 13 Aug 2026
  • LowCVE-2026-42297Argo has Missing Authorization in its Sync ConfigMap Provider in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42183Argo Affected by SSO RBAC Delegation Nil Pointer Dereference DoS (gatekeeper.go) in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42294Argo Vulnerable to Unauthenticated Memory Exhaustion (DoS) in Webhook Interceptor in github.com/argoproj/argo-workflows · 25 Jun 2026
  • LowCVE-2026-42295Argo vulnerable to exposure of artifact repository credentials in github.com/argoproj/argo-workflows · 25 Jun 2026
All 33 advisories for github.com/argoproj/argo-workflows/v3

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.