CVE-2026-119287
Zuke is a code-first, strongly typed build automation system for …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/zuke-build/zuke/commit/4257b0bc5ef5e387a44f913349646d4baccd1654
- github.com/zuke-build/zuke/pull/542
- github.com/zuke-build/zuke/releases/tag/core-v1.51.0
- github.com/zuke-build/zuke/security/advisories/GHSA-2rmh-5cw4-33gr
- nvd.nist.gov/vuln/detail/CVE-2026-119287
- cve.org/CVERecord?id=CVE-2026-119287
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.