CVE-2026-119287
Deferred Deferred - Pending Action

Remote Code Execution in Zuke Build Automation System

Publication date: 2026-10-30

Last updated on: 2026-10-30

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-30
Last Modified
2026-10-30
Generated
2026-10-30
AI Q&A
2026-10-30
EPSS Evaluated
N/A
NVD
CVE-2026-119287
EUVD
EUVD-2026-114132

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
zuke-build zuke < 1.51.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects Zuke, a build automation system for Deno. It allows a registry writer to execute arbitrary programs with the user's environment and workspace access by exploiting a flaw in the MCP registry mode. The issue occurs when the @zuke/core MCP registry mode accepts command-form registry descriptors without enforcing the ZUKE_REGISTRY_LAUNCH_HOSTS authorization applied to remote module descriptors.

Impact Analysis

If you use Zuke with the affected MCP registry mode, an attacker who controls a registry could run malicious programs on your system with your permissions. This could lead to unauthorized access, data theft, or system compromise. The vulnerability requires the attacker to have write access to a registry you use.

Compliance Impact

This vulnerability could lead to unauthorized code execution, potentially violating data protection requirements under GDPR or HIPAA. If exploited, it may result in unauthorized access to sensitive data, leading to compliance breaches and legal consequences.

Mitigation Strategies

Upgrade zuke to version 1.51.0 or later to address the vulnerability. Avoid using --registry and --allow-run flags with untrusted registries. Review registry descriptors for unauthorized commands.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119287. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart