Vulnerability in Zuke-Build Zuke
CVE-2026-119291
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.5 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Zuke-Build Zuke — versions < 1.4.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-119291?
- CVE-2026-119291 is a medium-severity vulnerability in Zuke-Build Zuke, classified under Improper Link Resolution Before File Access. CVSS score: 5.5/10. Published 2026-10-30.
- How severe is CVE-2026-119291?
- Medium severity. CVSS v3 base score is 5.5 out of 10.