Command Injection Affecting deno package, versions <2.7.10
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUST-DENO-17660654
- published27 Jun 2026
- disclosed16 Jun 2026
- creditUnknown
Introduced: 16 Jun 2026
NewCVE-2026-49402 (opens in a new tab)How to fix?
Upgrade deno to version 2.7.10 or higher.
Overview
deno is an a simple, modern and secure runtime for JavaScript and TypeScript that uses V8 and is built in Rust.
Affected versions of this package are vulnerable to Command Injection via the escapeShellArg process in Windows when using child_process with shell: true. An attacker can execute arbitrary commands and potentially leak environment variables by supplying specially crafted input containing cmd.exe metacharacters or environment variable references to the arguments passed to the process. This is only exploitable if the process is run on Windows and shell: true is set in the options.
Workaround
This vulnerability can be mitigated by avoiding the use of shell: true in node:child_process calls on Windows, building the argument vector directly and invoking the program without a shell, or filtering/rejecting externally-supplied argument values that contain cmd.exe metacharacters (& | < > ^ ! ( ) %) before passing them to spawn, spawnSync, or exec.