Zarf's symlink targets in archives are not validated against destination directory

Exploitation

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

CVSS

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

EPSS

• CVE-2026-29064: 0.26% estimated exploitation activity in the next 30 days; percentile 17.45 (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.

Summary A path traversal vulnerability in archive extraction allows a specifically crafted Zarf package to create symlinks pointing outside the destination directory, enabling arbitrary file read or write on the system processing the package. What users should do Upgrade immediately to version v0.73.1 If developers cannot upgrade immediately, only process Zarf packages from fully trusted sources until the fix is applied. If using trusted packages and archives - the only impact to this is updating zarf binary or SDK package versions. Previously created packages do not need to be rebuilt. Who is affected - Any user of affected Zarf versions who processes packages from untrusted or semi-trusted sources. This includes packages received via file transfer, downloaded from registries, or shared across organizational boundaries. This includes use of the zarf tools archiver decompress functionality on generic archives. - Any SDK consumers of Zarf for the affected versions who utilize package…

Published by the source

6 Mar 2026, 22:10 UTC

Last modified by the source

6 Mar 2026, 22:10 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hcm4-6hpj-vghm

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

# Patch Next advisory brief: CVE-2026-29064

Advisory: Zarf's symlink targets in archives are not validated against destination directory
IDs: CVE-2026-29064, GHSA-hcm4-6hpj-vghm
Record: https://patchnext.com/advisories/cve-2026-29064 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zarf-dev/zarf/src/pkg/archive 0.73.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zarf-dev/zarf/src/pkg/archive: affected >= 0.54.0, < 0.73.1; fixed in 0.73.1

## Suggested inspection (read-only)
- Go github.com/zarf-dev/zarf/src/pkg/archive: 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/zarf-dev/zarf/src/pkg/archive.
- 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-hcm4-6hpj-vghm (GitHub-reviewed advisory GHSA-hcm4-6hpj-vghm lists affected ranges: Go github.com/zarf-dev/zarf/src/pkg/archive >=0.54.0 <0.73.1)

Commands are suggestions: review each one before running it.