Skip to content
Fencer Vulns
high 8.1

CVE-2025-66626 json

argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links

published 2025-12-09 11 mo ago modified 2026-10-14 25 d ago also BIT-argo-workflows-2025-66626 , EUVD-2025-202177 , GHSA-xrqc-7xgx-c9vh , GO-2025-4223

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-workflows/v3 3.6.14, 3.7.5
  • bitnami argo-workflows 2.5.3, 3.6.14
  • argo_workflows_project argo_workflows 2.5.3-rc4, 3.6.14
  • argoproj argo_workflows 3.6.14
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-66626 updated cvss 8.1

github.com/argoproj/argo-workflows: argoproj/argo-workflows is vulnerable to RCE via ZipSlip and symbolic links

  • Red Hat OpenShift AI 2.16 rhoai 1774282136, rhoai 1774288148
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.” RHSA-2026:5807
  • Red Hat OpenShift AI 2.25 rhoai 1770223791, rhoai 1770223796, rhoai 1770223798, rhoai 1770223799, rhoai 1770224104, rhoai 1770224105, +8 more
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.” RHSA-2026:2695
  • Red Hat OpenShift AI 3.3 rhoai 1771363346, rhoai 1771363401, rhoai 1771363406, rhoai 1771363484, rhoai 1771377365, rhoai 1771420597, +1 more
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.” RHSA-2026:3713
  • Red Hat OpenShift AI 3.4 rhoai/odh-data-science-pipelines-argo-argoexec-rhel9 1787002529
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.” RHSA-2026:60520
  • Red Hat OpenShift AI 3.5 rhoai/odh-latency-predictor-training-rhel9 1786552250, rhoai/odh-latency-predictor-prediction-rhel9 1786552271
    fixed: vendor fix “No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.” RHSA-2026:60367
  • Red Hat OpenShift AI (RHOAI) rhoai/odh-ml-pipelines-driver-rhel8, rhoai/odh-ml-pipelines-launcher-rhel8, rhoai/odh-ml-pipelines-api-server-v2-rhel8, rhoai/odh-ml-pipelines-persistenceagent-v2-rhel8, rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel8
    not affected: vulnerable code not in execute path
  • Red Hat OpenShift AI 2.16 rhoai 1774282058, rhoai 1774282073, rhoai 1774282078, rhoai 1774282087, rhoai 1774282092, rhoai 1774282093, +18 more Red Hat OpenShift AI 2.25 rhoai 1770053626, rhoai 1770053627, rhoai 1770053694, rhoai 1770053703, rhoai 1770053721, rhoai 1770053723, +87 more Red Hat OpenShift AI 3.3 rhoai 1769162595, rhoai 1769436305, rhoai 1769519975, rhoai 1770277795, rhoai 1770735854, rhoai 1770754585, +65 more Red Hat OpenShift AI 3.4 rhoai/odh-cli-rhel9 1787330837, rhoai/rhai-cli-rhel9 1787330837, rhoai/odh-automl-rhel9 1786612415, rhoai/odh-mlflow-rhel9 1787226790, rhoai/odh-autorag-rhel9 1786612637, rhoai/odh-trainer-rhel9 1787089049, +99 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
10 mo ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/argoproj/argo-workflows/security/advisories/GHSA-xrqc-7xgx-c9vh referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/advisories/GHSA-p84v-gxvw-73pf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-workflows/v3
>=3.7.0, <3.7.5
<3.6.14
3.7.5
3.6.14
go github.com/argoproj/argo-workflows
<=2.5.3-rc4
all versions
 no fix listed
bitnami argo-workflows
<2.5.3
>=3.0.0, <3.6.14
2.5.3
3.6.14
go github.com/argoproj/argo-workflows/v2
all versions
 no fix listed

Affected products

  • argoproj argo-workflows

Classification

Weakness
  • CWE-23 Relative Path Traversal
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.