Zuke
Zuke: Command-form registry descriptors bypass the MCP launch policy
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.51.0
Fixed in 1.51.0
Mitigation
Upgrade zuke to 1.51.0 or later.
References
- Vendor advisory github.com/zuke-build/zuke/security/advisories…
- Patch github.com/zuke-build/zuke/pull/542
- Patch github.com/zuke-build/zuke/commit/4257b0bc5ef5…
1 more
- Release notes github.com/zuke-build/zuke/releases/tag/core-v…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.