CVE-2026-119291

zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory

Published Oct 30, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Zuke’s CLI uses lstat to examine scaffold names but then follows symbolic links when performing read and write operations during setup and import. An attacker who supplies a repository or template that contains a symlink to a file outside the intended target directory can cause the CLI to overwrite that external file with the user’s own permissions. This allows arbitrary file modification and the potential to inject executable code, representing an authorization bypass (CWE‑59) and a local privilege escalation vector.

Affected Systems

The vulnerability affects the zuke build automation system produced by zuke‑build. Any version of the zuke CLI released before v1.4.0 is susceptible. The issue was resolved in the 1.4.0 release and later.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity; the EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog. Exploitation requires an attacker capable of supplying a malicious repository, template, or archive to the local user running zuke. The attack vector is local, and the exploit would only succeed if the attacker can influence the input collection step (for example in continuous‑integration pipelines or local development).

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade zuke CLI to version 1.4.0 or later to apply the security fix.
  • If upgrading is not immediately possible, avoid using untrusted repositories or templates and do not enable the --force flag which allows writing linked launchers.
  • Ensure that symbolic links are not present in paths supplied to zuke by sanitizing input or configuring the build environment to reject or ignore symlinks.

Generated by OpenCVE AI on October 30, 2026 at 17:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zuke-build
Zuke-build zuke
Vendors & Products Zuke-build
Zuke-build zuke
Type Values Removed Values Added
Description 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.
Title zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory
Weaknesses CWE-59
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-59

    Improper Link Resolution Before File Access ('Link Following')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 4, 2026, 10:58 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Deferred
Published
Oct 30, 2026, 4:17 PM
Modified
Nov 4, 2026, 11:17 PM