UTC
High

GitHub Copilot CLI Dangerous Shell Expansion Patterns Enable Arbitrary Code Execution

CVE-2026-29783 · GHSA-g8r9-g2v8-jv6f · published 2026-03-06 · updated 2026-03-13

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.47%
Fixed in
0.0.423
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

An attacker who can influence command text sent to the shell tool — for example, through: Prompt injection via malicious repository content (README files, code comments, issue bodies) Compromised or malicious MCP server responses Crafted user instructions containing obfuscated commands — could achieve arbitrary code execution on the user's workstation. This is possible even in permission modes that require user approval for write operations, since the commands can appear to be using only read-only utilities to ultimately trigger write operations. Successful exploitation could lead to data exfiltration, file modification, or further system compromise.

What to do

Upgrade @github/copilot to 0.0.423 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

The fix adds three layers of defense: 1. Parse-time detection: The shell safety assessment analyzes ${...} expansion nodes within bash commands, detecting dangerous operators (@P, =, :=, !) and nested command/process substitutions. Commands containing these patterns are downgraded from read-only to write-capable, ensuring they require user approval. 2. Unconditional blocking: Commands with dangerous expansion patterns are unconditionally blocked at the tool execution layer — regardless of permission mode (including --yolo / autopilot). This prevents exploitation even when all commands are auto-approved. 3.

Affected
PackageRegistryAffectedFixed in
@github/copilotnpm<= 0.0.4220.0.423

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].