<?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 09:19:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-280517</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-280517</link>
      <description>EUVD-2026-280517</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-280517</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34768</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34768</link>
      <description>&lt;p&gt;Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8, on Windows, app.setLoginItemSettings({openAtLogin: true}) wrote the executable path to the Run registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app. On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8, on Windows, app.setLoginItemSettings({openAtLogin: true}) wrote the executable path to the Run registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app. On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location. This issue has been patched in versions 38.8.6, 39.8.1, 40.8.0, and 41.0.0-beta.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34768</guid>
    </item>
    <item>
      <title>GHSA-jfqx-fxh3-c62j — Electron: Unquoted executable path in app.setLoginItemSettings on Windows</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jfqx-fxh3-c62j</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: electron&lt;/p&gt;
&lt;p&gt;### Impact
On Windows, `app.setLoginItemSettings({openAtLogin: true})` wrote the executable path to the `Run` registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app.&lt;/p&gt;
&lt;p&gt;On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location.&lt;/p&gt;
&lt;p&gt;### Workarounds
Install the application to a path without spaces, or to a location where all ancestor directories are protected against unauthorized writes.&lt;/p&gt;
&lt;p&gt;### Fixed Versions
* `41.0.0-beta.8`
* `40.8.0`
* `39.8.1`
* `38.8.6`&lt;/p&gt;
&lt;p&gt;### For more information
If there are any questions or comments about this advisory, send an email to [security@electronjs.org](mailto:security@electronjs.org)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: electron&lt;/p&gt;
&lt;p&gt;### Impact
On Windows, `app.setLoginItemSettings({openAtLogin: true})` wrote the executable path to the `Run` registry key without quoting. If the app is installed to a path containing spaces, an attacker with write access to an ancestor directory may be able to cause a different executable to run at login instead of the intended app.&lt;/p&gt;
&lt;p&gt;On a default Windows install, standard system directories are protected against writes by standard users, so exploitation typically requires a non-standard install location.&lt;/p&gt;
&lt;p&gt;### Workarounds
Install the application to a path without spaces, or to a location where all ancestor directories are protected against unauthorized writes.&lt;/p&gt;
&lt;p&gt;### Fixed Versions
* `41.0.0-beta.8`
* `40.8.0`
* `39.8.1`
* `38.8.6`&lt;/p&gt;
&lt;p&gt;### For more information
If there are any questions or comments about this advisory, send an email to [security@electronjs.org](mailto:security@electronjs.org)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jfqx-fxh3-c62j</guid>
    </item>
  </channel>
</rss>
