# CVE-2026-29064: Zarf: Symlink targets in archives are not validated against destination directory

> A path traversal flaw in Zarf allows crafted packages to create symlinks outside the destination, enabling arbitrary file read or write.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-hcm4-6hpj-vghm, GO-2026-4636

## What is CVE-2026-29064?

CVE-2026-29064 is a high-severity path traversal vulnerability in zarf-dev zarf, published on 6 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-29064?

3 open source packages ship an affected version, including github.com/zarf-dev/zarf/src/pkg/archive and github.com/zarf-dev/zarf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zarf-dev/zarf/src/pkg/archive` | Go | From 0.54.0 | 0.73.1 |
| `github.com/zarf-dev/zarf/src/pkg/archive` | Go | From 0.54.0 | 0.73.1 |
| `github.com/zarf-dev/zarf` | Go | From 0.54.0 | 0.73.1 |

Products: Lfprojects Zarf.

## How do I fix CVE-2026-29064?

Upgrade github.com/zarf-dev/zarf/src/pkg/archive to 0.73.1 or later.

## Is CVE-2026-29064 being exploited?

There is no known exploitation of CVE-2026-29064 in the wild and no public exploit code.

## Other vulnerabilities in zarf-dev zarf

- [CVE-2026-40090](https://insights.sbomify.com/CVE-2026-40090/): Zarf has a Path Traversal via Malicious Package Metadata.Name — Arbitrary File Write (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29064 and fix it if it is affected.

What it is: CVE-2026-29064 is a high-severity path traversal vulnerability in zarf-dev zarf, published on 6 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-29064 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zarf-dev/zarf/src/pkg/archive (Go): affected from 0.54.0; fixed in 0.73.1
- github.com/zarf-dev/zarf/src/pkg/archive (Go): affected from 0.54.0; fixed in 0.73.1
- github.com/zarf-dev/zarf (Go): affected from 0.54.0; fixed in 0.73.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29064/ (Markdown: https://insights.sbomify.com/CVE-2026-29064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29064
- OSV: https://osv.dev/vulnerability/CVE-2026-29064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29064/
Summaries are generated and may contain mistakes; the official description above is the record.