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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-59"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/119xxx/CVE-2026-119291.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.4.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "4257b0bc5ef5e387a44f913349646d4baccd1654"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "cli-v1.4.0",
"range": [
{
"fixed": "f68ed95ace4ae78b28f9bcb67c84f49016bbe7a3"
}
],
"source": "REFERENCES_TAG"
}
]
}