Is this vulnerability remotely exploitable?

It can be remotely exploitable if an attacker can deliver a crafted Zarf package to a system that automatically or routinely processes such packages, for example via a CI/CD pipeline or artifact repository. The actual extraction still occurs locally on the host running Zarf.

What level of access does an attacker need?

An attacker needs the ability to create, modify, or influence a Zarf package that will be processed by an affected Zarf instance. Direct shell access is not required; control over the package contents is sufficient.

What is the safest general fix pattern?

The safest pattern is to strictly confine all extracted paths to a designated directory: normalize paths, resolve symlinks, and reject any entry that escapes the target root. Additionally, avoid using symlink targets from packages for operations that affect the broader host filesystem.

Severity:

HIGH RISK

(8.2)

Path Traversal via Symlink Extraction (CWE-22) in Zarf Package Handling

CVE-2026-29064

Published:

Mar 6, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22

Impact:

Arbitrary File Read/Write on the Host System

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Vulnerability Type

Category:

Path Traversal / Directory Traversal

CWE:

CWE-22

Impact:

Arbitrary File Read/Write on the Host System

Severity:

HIGH RISK

(8.2)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Path Traversal via Symlink Extraction (CWE-22) in Zarf Package Handling

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare