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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.5 · zuke-buildNVD modified 2026-10-30 15:52
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://github.com/zuke-build/zuke/security/advisories/GHSA-hc8w-3fgv-22pw x_refsource_confirm
- https://github.com/zuke-build/zuke/pull/542 x_refsource_misc
- https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654 x_refsource_misc
- https://github.com/zuke-build/zuke/releases/tag/cli-v1.4.0 x_refsource_misc