Skip to content
Fencer Vulns
high 8.2

CVE-2026-29064 json

Zarf: Symlink targets in archives are not validated against destination directory

published 2026-03-06 8 mo ago modified 2026-06-17 4 mo ago also GHSA-hcm4-6hpj-vghm , GO-2026-4636 , EUVD-2026-10044

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

Summary

Zarf is an Airgap Native Packager Manager for Kubernetes. From version 0.54.0 to before version 0.73.1, 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. This issue has been patched in version 0.73.1.

Patch / fix

  • go github.com/zarf-dev/zarf/src/pkg/archive 0.73.1
  • go github.com/zarf-dev/zarf 0.73.1
  • lfprojects zarf 0.73.1
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1

suse advisories SUSE-SU-2026:1042-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
8 mo ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/zarf-dev/zarf/security/advisories/GHSA-hcm4-6hpj-vghm referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
GitHub 3.1 8.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/zarf-dev/zarf/src/pkg/archive
>=0.54.0, <0.73.1
0.73.1
go github.com/zarf-dev/zarf
>=0.54.0, <0.73.1
0.73.1

Affected products

  • zarf-dev zarf

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.