CVE-2025-61787: Deno Deno Is Vulnerable To Command Vulnerability

HIGH
Advisory Identifier: GHSA-m2gf-x3f6-8hq3
Share
CVSS 8.1
CWE-77
Published
Advisory Summary

CVE-2025-61787 is a HIGH (CVSS 8.1) deno is vulnerable to command vulnerability (CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')) affecting Deno libraries in the crates.io ecosystem. The issue involves deno is vulnerable to command injection on windows during batch file execution. Remediation is available by upgrading affected packages to version 2.5.2.

CVE-2025-61787 at a Glance

CVE Identifier CVE-2025-61787
GHSA Identifier GHSA-m2gf-x3f6-8hq3
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection')
Affected Product Deno
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2025-61787

To remediate this vulnerability, upgrade all affected Deno dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

deno fixed: 2.5.2 
Upgrade deno to 2.5.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for deno

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-61787, inspect your project dependencies for Deno:

inspect dependencies for deno

Analyze the terminal output to locate any version of Deno in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection'), where the product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. In Deno, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary Deno versions up to 2.5.1 are vulnerable to Command Line Injection attacks on Windows when batch files are executed. ### Details 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 as demonstrated by the two proves-of-concept below. ### PoC Using `node:child_process` (with the `env` and `run` permissions): ```JS const { spawn } = require('node:child_process'); const child = spawn('./test.bat', ['&calc.exe']); ``` Using `Deno.Command.spawn()` (with the `run` permission): ```JS const command = new Deno.Command('./test.bat', { args: ['&calc.exe'], }); const child = command.spawn(); ``` ### Impact Both of these scripts result in opening calc.exe on Windows, thus allowing a Command Line Injection attack when user-provided arguments are passed if the script being executed by the child process is a batch script.

CVE-2025-61787 Affected Deno Versions

1 component(s)
Fixed Versions:
2.5.2
Product / Package Ecosystem Affected Versions Fixed Version
deno
 crates.io
< 2.5.2
2.5.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/denoland/deno/security/advisories/GHSA-m2gf-x3f6-8hq3
NVD — CVE-2025-61787 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-61787
Deno Source Repository REPOSITORY
https://github.com/denoland/deno/pull/30818
Security Fix Commit FIX COMMIT
https://github.com/denoland/deno/commit/8a0990ccd37bafd8768176ca64b906ba2da2d822
Deno Source Repository REPOSITORY
https://github.com/denoland/deno
Deno Release RELEASE
https://github.com/denoland/deno/releases/tag/v2.2.15
Deno Release RELEASE
https://github.com/denoland/deno/releases/tag/v2.5.2

Frequently Asked Questions

What is CVE-2025-61787?
CVE-2025-61787 is a security vulnerability in Deno involving Deno is Vulnerable to Command Injection on Windows During Batch File Execution under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection').
Which Deno versions are affected?
Affected versions include releases prior to 2.5.2 across affected packages: deno.
What version fixes CVE-2025-61787?
Upgrading to 2.5.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is deno affected?
Yes, deno is affected in releases prior to 2.5.2. Upgrade your dependency to 2.5.2 or later.
What is the CVSS score of CVE-2025-61787?
CVE-2025-61787 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2025-61787?
CVE-2025-61787 is classified under CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') (The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.).
How can I check crates.io dependencies for CVE-2025-61787?
Run the dependency tree command: 'inspect dependencies for deno'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m2gf-x3f6-8hq3",
  "modified" : "2025-10-08T18:16:24Z",
  "published" : "2025-10-08T18:16:24Z",
  "aliases" : [ "CVE-2025-61787" ],
  "summary" : "Deno is Vulnerable to Command Injection on Windows During Batch File Execution",
  "details" : "### Summary\nDeno versions up to 2.5.1 are vulnerable to Command Line Injection attacks on Windows when batch files are executed.\n\n### Details\nIn 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 as demonstrated by the two proves-of-concept below.\n\n### PoC\nUsing `node:child_process` (with the `env` and `run` permissions):\n```JS\nconst { spawn } = require('node:child_process');\nconst child = spawn('./test.bat', ['&calc.exe']);\n```\nUsing `Deno.Command.spawn()` (with the `run` permission):\n```JS\nconst command = new Deno.Command('./test.bat', {\n  args: ['&calc.exe'],\n});\nconst child = command.spawn();\n```\n\n### Impact\nBoth of these scripts result in opening calc.exe on Windows, thus allowing a Command Line Injection attack when user-provided arguments are passed if the script being executed by the child process is a batch script.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "deno"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.5.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/denoland/deno/security/advisories/GHSA-m2gf-x3f6-8hq3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-61787"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/denoland/deno/pull/30818"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/denoland/deno/commit/8a0990ccd37bafd8768176ca64b906ba2da2d822"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/denoland/deno"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/denoland/deno/releases/tag/v2.2.15"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/denoland/deno/releases/tag/v2.5.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-77" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-10-08T18:16:24Z",
    "nvd_published_at" : "2025-10-08T02:15:41Z"
  }
}