Technical impact
The vulnerability in Zuke allows a registry writer to supply command‑form descriptors that bypass the MCP launch policy. This permits arbitrary program execution with the operator’s environment and workspace, effectively enabling an attacker to gain code execution permissions. The flaw originates from the lack of enforcement of the ZUKE_REGISTRY_LAUNCH_HOSTS authorization on command‑form descriptors, categorized as an authorization bypass (CWE-862). If exploited, the attacker can compromise confidentiality, integrity, and availability of the operator’s system.
Affected Systems
The affected product is Zuke, a code‑first build automation system for Deno, produced by zuke-build. Versions before 1.51.0 are impacted, including all releases that implement the @zuke/core MCP registry mode without enforcing the launch host policy. The issue is resolved in version 1.51.0 and later.
Risk and Exploitability
The CVSS score is 8, indicating high severity. The EPSS score is not available, so the current exploitation probability cannot be quantified. The vulnerability is not listed in the CISA KEV catalog. Exploitation requires the ability to write command‑form registry descriptors or to trick the operator into running a malicious registry. If a malicious party has write access to the registry or can supply a remote descriptor, the attack path involves invoking zuke mcp with --registry and --allow-run; the malicious descriptor then spawns arbitrary commands in the operator’s environment. Because the flaw offers control over both the program and its arguments, successful exploitation results in full code execution on the operator’s system.