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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.0 · zuke-buildNVD modified 2026-10-30 15:39
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://github.com/zuke-build/zuke/security/advisories/GHSA-2rmh-5cw4-33gr x_refsource_confirm
- https://github.com/zuke-build/zuke/pull/542 x_refsource_misc
- https://github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654 x_refsource_misc
- https://github.com/zuke-build/zuke/releases/tag/core-v1.51.0 x_refsource_misc