CVE-2026-119291
zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| zuke zuke-build |
< 1.4.0 (affected) | CNA: GitHub_M |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 5.5 medium |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N | CNA: GitHub_M |
| 3.1 / 5.5 medium |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/zuke-build/zuke/security/advisories/GHSA-hc8w-3fgv-22pwCNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/zuke-build/zuke/pull/542CNA: GitHub_M · x_refsource_MISC
- https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654CNA: GitHub_M · x_refsource_MISC
- https://github.com/zuke-build/zuke/releases/tag/cli-v1.4.0CNA: GitHub_M · x_refsource_MISC
- https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654[email protected]
- https://github.com/zuke-build/zuke/pull/542[email protected]
- https://github.com/zuke-build/zuke/releases/tag/cli-v1.4.0[email protected]
- https://github.com/zuke-build/zuke/security/advisories/GHSA-hc8w-3fgv-22pw[email protected]
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.