deno
Affected
- introduced
2.7.0, fixed2.7.2(semver)
Fixed versions
2.7.2
Fix
- Fixed version
2.7.2cargo update -p deno --precise 2.7.2
Advisory
Also known as: CVE-2026-32260
Deno vulnerable to command Injection via incomplete shell metacharacter blocklist in node:child_process
Summary
A command injection vulnerability exists in Deno's node:child_process polyfill (shell: true mode) that bypasses the fix
for CVE-2026-27190 (GHSA-hmh4-3xvx-q5hr). An attacker who controls arguments passed to spawnSync or spawn with `shell:
true` can execute arbitrary OS commands, bypassing Deno's permission system.
Affected versions: Deno v2.7.0, v2.7.1
## Details
The two-stage argument sanitization in transformDenoShellCommand (ext/node/polyfills/internal/child_process.ts) has a
priority bug: when an argument contains a $VAR pattern, it is wrapped in double quotes (L1290) instead of single quotes
(L1293). Double quotes in POSIX sh do not suppress backtick command substitution, allowing injected commands to execute.
Attack chain:
escapeShellArg wraps the argument in single quotes (safe)op_node_parse_shell_args strips the single-quote delimiters during tokenization (raw argument exposed)$VAR pattern → applies double quotes/bin/sh## Impact
OS Command Injection (CWE-78). Any application using node:child_process spawn/spawnSync with shell: true and
user-controlled arguments is vulnerable. Injected commands execute at the OS process level, outside Deno's permission
sandbox. Only --allow-run is required.
## Mitigation
Avoid passing user-controlled input as arguments to spawn/spawnSync with shell: true. Use shell: false (the default)
instead, or validate/sanitize inputs before passing them.
High Basis: The source's own band: HIGH
2.7.0, fixed 2.7.2 (semver)2.7.2
2.7.2cargo update -p deno --precise 2.7.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0