| Package | Affected versions | Patched versions |
|---|---|---|
| copilot command line interface | < 0.0.423 | 0.0.423 |
| @github/copilot | < 0.0.423 | 0.0.423 |
A security vulnerability has been identified in GitHub Copilot CLI's shell tool that could allow arbitrary code execution through crafted bash parameter expansion patterns. An attacker who can influence the commands executed by the agent (e.g., via prompt injection through repository files, MCP server responses, or user instructions) can exploit bash parameter transformation operators to execute hidden commands, bypassing the safety assessment that classifies commands as "read-only."
The vulnerability stems from how the CLI's shell safety assessment evaluates commands before execution. The safety layer parses and classifies shell commands as either read-only (safe) or write-capable (requires user approval). However, several bash parameter expansion features can embed executable code within arguments to otherwise read-only commands, causing them to appear safe while actually performing arbitrary operations.
The specific dangerous patterns are:
${var@P} — Prompt expansion: The @P parameter transformation operator evaluates its value as a prompt string, which interprets embedded command substitutions. This allows hidden command execution inside what appears to be a simple variable reference.
${var=value} / — Assignment side-effects: These forms assign values to variables as a side-effect of expansion. When chained with , an attacker can progressively build up a command substitution string across multiple expansions.
${var:=value}@P${!var} — Indirect expansion: Dereferences an arbitrary variable name, which can be combined with other patterns to construct and execute commands dynamically.
Nested $(cmd) or <(cmd) inside ${...} expansions: Command substitution or process substitution embedded within parameter expansion default values (e.g., ${HOME:-$(whoami)}) executes the nested command.
The following command appears to run a harmless echo, but actually executes touch /tmp/pwned through chained parameter expansion:
echo ${a="$"}${b="$a(touch /tmp/pwned)"}${b@P}
How it works:
${a="$"} assigns the literal $ character to variable a${b="$a(touch /tmp/pwned)"} expands $a to $, constructing the string $(touch /tmp/pwned) and assigning it to b${b@P} applies prompt expansion to b, which evaluates the embedded $(touch /tmp/pwned) command substitutionPrior to the fix, the safety assessment would classify echo as a read-only command and allow execution without user confirmation — even in modes that normally require approval for write operations.
An attacker who can influence command text sent to the shell tool — for example, through:
— 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.
The fix adds three layers of defense:
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.
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.
System prompt hardening: The bash shell tool's system prompt now includes explicit instructions for the LLM to refuse executing commands with these patterns, providing a defense-in-depth layer.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free