<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 05:56:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-254456</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-254456</link>
      <description>EUVD-2026-254456</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-254456</guid>
    </item>
    <item>
      <title>fkie_cve-2025-61787</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-61787</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-61787</guid>
    </item>
    <item>
      <title>GHSA-m2gf-x3f6-8hq3 — Deno is Vulnerable to Command Injection on Windows During Batch File Execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m2gf-x3f6-8hq3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno&lt;/p&gt;
&lt;p&gt;### Summary
Deno versions up to 2.5.1 are vulnerable to Command Line Injection attacks on Windows when batch files are executed.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### PoC
Using `node:child_process` (with the `env` and `run` permissions):
```JS
const { spawn } = require(&amp;#39;node:child_process&amp;#39;);
const child = spawn(&amp;#39;./test.bat&amp;#39;, [&amp;#39;&amp;amp;calc.exe&amp;#39;]);
```
Using `Deno.Command.spawn()` (with the `run` permission):
```JS
const command = new Deno.Command(&amp;#39;./test.bat&amp;#39;, {
  args: [&amp;#39;&amp;amp;calc.exe&amp;#39;],
});
const child = command.spawn();
```&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: deno&lt;/p&gt;
&lt;p&gt;### Summary
Deno versions up to 2.5.1 are vulnerable to Command Line Injection attacks on Windows when batch files are executed.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### PoC
Using `node:child_process` (with the `env` and `run` permissions):
```JS
const { spawn } = require(&amp;#39;node:child_process&amp;#39;);
const child = spawn(&amp;#39;./test.bat&amp;#39;, [&amp;#39;&amp;amp;calc.exe&amp;#39;]);
```
Using `Deno.Command.spawn()` (with the `run` permission):
```JS
const command = new Deno.Command(&amp;#39;./test.bat&amp;#39;, {
  args: [&amp;#39;&amp;amp;calc.exe&amp;#39;],
});
const child = command.spawn();
```&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m2gf-x3f6-8hq3</guid>
    </item>
  </channel>
</rss>
