CVE-2026-119291
Zuke is a code-first, strongly typed build automation system for …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654
- github.com/zuke-build/zuke/pull/542
- github.com/zuke-build/zuke/releases/tag/cli-v1.4.0
- github.com/zuke-build/zuke/security/advisories/GHSA-hc8w-3fgv-22pw
- nvd.nist.gov/vuln/detail/CVE-2026-119291
- cve.org/CVERecord?id=CVE-2026-119291
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.