<?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://db.gcve.eu</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>Thu, 22 Oct 2026 00:20:56 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-112943</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-112943</link>
      <description>&lt;p&gt;launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, launch-editor did not escape % on Windows when passing an argument to cmd. When an environment variable contained a malicious value, it was possible that that content to be executed. This vulnerability is fixed in 2.14.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;launch-editor allows users to open files with line numbers in editor from Node.js. Prior to 2.14.2, launch-editor did not escape % on Windows when passing an argument to cmd. When an environment variable contained a malicious value, it was possible that that content to be executed. This vulnerability is fixed in 2.14.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-112943</guid>
    </item>
    <item>
      <title>GHSA-698v-4r3x-3vcv — launch-editor: escapeCmdArgs() omits % escaping on Windows</title>
      <link>https://db.gcve.eu/vuln/ghsa-698v-4r3x-3vcv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: launch-editor, npm: vite, npm: vite-plus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`launch-editor` did not escape `%` on Windows when passing an argument to `cmd`. When an environment variable contained a malicious value, it was possible that that content to be executed.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Only apps that match all of the following conditions are affected:&lt;/p&gt;
&lt;p&gt;- The user uses Windows
- An attacker can place a file with the malicious filename containing `&amp;amp;` or `%`
- Either of
  - An attacker can inject an environment variable with a malicious value
  - An attacker can add a NTFS alternate data stream to the file placed&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Unlike `.sh` files, `.bat` / `.cmd` files on Windows cannot be called directly using [`child_process.spawn`](https://nodejs.org/docs/latest-v24.x/api/child_process.html#child_processspawncommand-args-options) and requires passing them as an argument of `cmd.exe`. To do so, launch-editor escapes the arguments passed to `cmd.exe`. But `launch-editor` did not escape `%` which is used for environment variables.&lt;/p&gt;
&lt;p&gt;Because `launch-editor` checks if the argument matches an existing filename, the attack requires the attacker to be able to place a file.&lt;/p&gt;
&lt;p&gt;- If the attacker can inject an environment variable as well, they can include the subcommand in the env variable (e.g. set ` &amp;amp;calc.exe ` to `%ENV%`) and call `launchEditor` with `something%ENV%`.
- If the attacker can place a NTFS alternate data stream to the file (e.g. a NTFS alternate data stream named `~-38%calc.exe`), they can call `launchEditor` with `something %CMDCMDLINE:~-38%c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: launch-editor, npm: vite, npm: vite-plus&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;`launch-editor` did not escape `%` on Windows when passing an argument to `cmd`. When an environment variable contained a malicious value, it was possible that that content to be executed.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Only apps that match all of the following conditions are affected:&lt;/p&gt;
&lt;p&gt;- The user uses Windows
- An attacker can place a file with the malicious filename containing `&amp;amp;` or `%`
- Either of
  - An attacker can inject an environment variable with a malicious value
  - An attacker can add a NTFS alternate data stream to the file placed&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Unlike `.sh` files, `.bat` / `.cmd` files on Windows cannot be called directly using [`child_process.spawn`](https://nodejs.org/docs/latest-v24.x/api/child_process.html#child_processspawncommand-args-options) and requires passing them as an argument of `cmd.exe`. To do so, launch-editor escapes the arguments passed to `cmd.exe`. But `launch-editor` did not escape `%` which is used for environment variables.&lt;/p&gt;
&lt;p&gt;Because `launch-editor` checks if the argument matches an existing filename, the attack requires the attacker to be able to place a file.&lt;/p&gt;
&lt;p&gt;- If the attacker can inject an environment variable as well, they can include the subcommand in the env variable (e.g. set ` &amp;amp;calc.exe ` to `%ENV%`) and call `launchEditor` with `something%ENV%`.
- If the attacker can place a NTFS alternate data stream to the file (e.g. a NTFS alternate data stream named `~-38%calc.exe`), they can call `launchEditor` with `something %CMDCMDLINE:~-38%c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-698v-4r3x-3vcv</guid>
    </item>
  </channel>
</rss>
