---
id: "CVE-2026-119291"
kind: "vulnerability"
aliases: ["CVE-2026-119291"]
title: "Zuke build tool: symlinks let setup overwrite files outside the project"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["build-tools", "deno", "package", "zuke"]
not_affected_if: ["does-not-use-zuke", "only-trusted-input"]
published_at: "2026-10-30T16:17:43+00:00"
first_seen_at: "2026-10-30T16:31:25+00:00"
updated_at: "2026-10-30T16:32:24+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119291", "first_seen_at": "2026-10-30T16:31:25+00:00"}]
---

# Zuke build tool: symlinks let setup overwrite files outside the project

Zuke is a Deno build automation tool whose CLI checks scaffold names with lstat but then follows symbolic links when reading, writing and changing permissions during zuke setup and zuke import. A malicious cloned repository, template or archive containing a symlink can make the tool overwrite files outside the chosen directory and read link-target content into a generated build file, with the invoking user's permissions.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether the project depends on `@zuke/cli` and which version is installed, for example with `deno info` or the lockfile.
- Look at whether `zuke setup` or `zuke import` has been run against untrusted repositories, templates or archives.

## Fix

- `@zuke/cli`: move to `1.4.0`

## Timeline

- 2026-10-30T16:31:25+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119291

## From the sources

Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.4.0, @zuke/cli uses lstat to inspect scaffold names but then performs link-following reads, writes, and permission changes in zuke setup and zuke import. An attacker who supplies an untrusted cloned repository, template, or archive with a symbolic link at a scaffolded name can cause setup to overwrite a target outside the selected directory with the invoking user's permissions. The .gitignore path requires no flag, while --force permits a linked launcher target to be written and made executable; import can also read link-target content and incorporate it into the generated build file. This issue is fixed in version 1.4.0.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_