CVE-2025-61787: denoland deno · Command Injection
Affects denoland denoSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 2.2.15 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 2.0% chance of exploitation in 30 days – higher than 81% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.2.15
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade denoland deno to 2.2.15.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| denoland deno | Affected
| Fixed in
|
AI-suggested
1. Immediately upgrade all Deno installations on Windows to versions 2.5.3 or 2.2.15 or later to apply the official patch. 2. Audit all codebases and scripts that invoke batch files or shell commands within Deno to ensure no untrusted input is passed without proper sanitization or escaping. 3. Implement strict input validation and use safe APIs that avoid shell invocation when possible. 4. Employ application whitelisting and endpoint protection solutions to detect and block suspicious command execution patterns. 5. Monitor logs for unusual cmd.exe invocations or batch file executions originating from Deno processes. 6. Restrict permissions for Deno runtime environments to minimize the impact of potential exploitation. 7. Educate developers about the risks of command injection and secure coding practices related to system command execution. 8. Consider isolating Deno workloads in containerized or sandboxed environments to limit lateral movement in case of compromise.
Description
Deno is a JavaScript, TypeScript, and WebAssembly runtime. Versions prior to 2.5.3 and 2.2.15 are vulnerable to Command Line Injection attacks on Windows when batch files are executed. In Windows, ``CreateProcess()`` always implicitly spawns ``cmd.exe`` if a batch file (.bat, .cmd, etc.) is being executed even if the application does not specify it via the command line. This makes Deno vulnerable to a command injection attack on Windows. Versions 2.5.3 and 2.2.15 fix the issue.
References
- github.com/denoland/deno/security/advisories/GHSA-m2gf-x3f6-8hq3 (opens in a new tab)
- github.com/denoland/deno/pull/30818 (opens in a new tab)
- github.com/denoland/deno/commit/8a0990ccd37bafd8768176ca64b906ba2da2d822 (opens in a new tab)
- github.com/denoland/deno/releases/tag/v2.2.15 (opens in a new tab)
- github.com/denoland/deno/releases/tag/v2.5.3 (opens in a new tab)