Approved changes feed: RSS · Atom

cpe:2.3:a:zuke-build:zuke:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorZuke Build (aef4932a-109d-5ec4-90c7-7563424cedbf)
ProductZuke (3d74dfe3-1193-5568-ba92-13e74d9667df)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-119287 vulnerable 2026-11-19 05:28:54.368114 Zuke: Command-form registry descriptors bypass the MCP launch policy
HIGH (8)
Zuke is a code-first, strongly typed build automation system for Deno. Prior to 1.51.0, the @zuke/core MCP registry mode accepts command-form registry descriptors without applying the ZUKE_REGISTRY_LAUNCH_HOSTS authorization enforced for remote module descriptors. When zuke mcp --registry --allow-run reads a registry writable by another party and a run-capable caller invokes the affected tool, the registry writer can choose the program and arguments executed with the operator's environment and workspace access. The --allow-run and --protect name globs do not contain the issue because the descriptor supplies those names, and the optional destructive confirmation displays a description controlled by the same writer. The local default registry populated only through zuke register is not affected because that command writes module-form descriptors. This issue is fixed in version 1.51.0.
Published: 2026-10-30T15:39:52.468Z
Updated: 2026-11-04T22:57:38.406Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-119291 vulnerable 2026-11-19 05:28:54.075918 zuke setup and zuke import follow symbolic links planted at scaffold names, allowing writes outside the target directory
MEDIUM (5.5)
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: 2026-10-30T15:52:01.029Z
Updated: 2026-11-04T22:58:47.426Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.