CVE-2026-119287
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.
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.51.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 / 8.0 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H | CNA: GitHub_M |
| 3.1 / 8.0 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H | 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-2rmh-5cw4-33grCNA: 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/core-v1.51.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/core-v1.51.0[email protected]
- https://github.com/zuke-build/zuke/security/advisories/GHSA-2rmh-5cw4-33gr[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.