Argo Workflow has a Zipslip Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2025-62156: 0.60% estimated exploitation activity in the next 30 days; percentile 48.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability Description Vulnerability Overview 1. During the artifact extraction process, the unpack() function extracts the compressed file to a temporary directory (/etc.tmpdir) and then attempts to move its contents to /etc using the rename() system call, 2. However, since /etc is an already existing system directory, the rename() system call fails, making normal archive extraction impossible. 3. At this point, if a malicious user sets the entry name inside the tar.gz file to a path traversal like ../../../../../etc/zipslip-poc, 4. The untar() function combines paths using filepath.Join(dest, filepath.Clean(header.Name)) without path validation, resulting in target = "/work/input/../../../../../etc/zipslip-poc", 5. Ultimately, the /etc/zipslip-poc file is created, bypassing the normal archive extraction constraints and enabling direct file writing to system directories. untar(): Writing Files Outside the Extraction Directory…

Published by the source

14 Oct 2025, 18:00 UTC

Last modified by the source

5 Nov 2025, 22:10 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p84v-gxvw-73pf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-62156

Advisory: Argo Workflow has a Zipslip Vulnerability
IDs: CVE-2025-62156, GHSA-p84v-gxvw-73pf
Record: https://patchnext.com/advisories/cve-2025-62156 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/argoproj/argo-workflows/v3 3.7.3, 3.6.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-workflows/v3: affected < 3.6.12; >= 3.7.0, < 3.7.3; fixed in 3.6.12, 3.7.3

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-workflows/v3: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-workflows/v3.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p84v-gxvw-73pf (GitHub-reviewed advisory GHSA-p84v-gxvw-73pf lists affected ranges: Go github.com/argoproj/argo-workflows/v3 >=0 =3.7.0 <3.7.3)

Commands are suggestions: review each one before running it.