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).