CVE-2026-119287

Zuke: Command-form registry descriptors bypass the MCP launch policy

Published Oct 30, 2026 CVSS 3.1 · 8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Zuke to version 1.51.0 or later to apply the fixed policy enforcement.
  • Restrict access to the registry directory so that only trusted users can write command‑form descriptors.
  • Avoid running zuke mcp with the --allow-run flag on registries that are writable by untrusted parties.
  • If upgrading is not possible immediately, remove the --allow-run flag and avoid executing code sourced from untrusted registries.

Generated by OpenCVE AI on October 30, 2026 at 16:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zuke-build
Zuke-build zuke
Vendors & Products Zuke-build
Zuke-build zuke
Type Values Removed Values Added
Description 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.
Title Zuke: Command-form registry descriptors bypass the MCP launch policy
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 4, 2026, 10:57 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Deferred
Published
Oct 30, 2026, 4:17 PM
Modified
Nov 4, 2026, 11:17 PM