Advisory

GHSA-xrqc-7xgx-c9vh

Also known as: BIT-argo-workflows-2025-66626, CVE-2025-66626, GO-2025-4223

Summary

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

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-12-09 17:17 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.7.0, fixed 3.7.5 (semver)

Fixed versions

3.7.5

Fix

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 0, fixed 3.6.14 (semver)

Fixed versions

3.6.14

Fix

github.com/argoproj/argo-workflows

Go · All systems

Affected

  • introduced 0, last affected 2.5.3-rc4 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences