<?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>Wed, 30 Sep 2026 14:45:42 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-102673</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-102673</link>
      <description>&lt;p&gt;Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to 41.10.4, 42.5.2, and 43.0.0, popups opened from a sandboxed iframe through Electron&amp;#39;s OpenURLFromTab navigation path, including links using target=&amp;#34;_blank&amp;#34; or a middle-click, did not receive the inherited HTML sandbox restrictions. An untrusted iframe using the allow-scripts allow-popups configuration could therefore open a popup with the embedding application&amp;#39;s full origin, exposing that origin&amp;#39;s cookies, storage, and same-origin scripting capabilities. Applications that do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in versions 41.10.4, 42.5.2, and 43.0.0.&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 41.10.4, 42.5.2, and 43.0.0, popups opened from a sandboxed iframe through Electron&amp;#39;s OpenURLFromTab navigation path, including links using target=&amp;#34;_blank&amp;#34; or a middle-click, did not receive the inherited HTML sandbox restrictions. An untrusted iframe using the allow-scripts allow-popups configuration could therefore open a popup with the embedding application&amp;#39;s full origin, exposing that origin&amp;#39;s cookies, storage, and same-origin scripting capabilities. Applications that do not embed untrusted content in sandboxed iframes are not affected. This issue is fixed in versions 41.10.4, 42.5.2, and 43.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-102673</guid>
    </item>
    <item>
      <title>GHSA-hq2x-r82h-9wj4 — Electron drops inherited HTML sandbox restrictions for popups opened through OpenURLFromTab</title>
      <link>https://db.gcve.eu/vuln/ghsa-hq2x-r82h-9wj4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: electron&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Popups opened from a sandboxed iframe through a link (for example `target=&amp;#34;_blank&amp;#34;` or a middle-click) did not inherit the iframe&amp;#39;s HTML `sandbox` restrictions. Content that was meant to run sandboxed could open a popup with the embedding app&amp;#39;s full origin, gaining access to that origin&amp;#39;s cookies, storage, and same-origin scripting.&lt;/p&gt;
&lt;p&gt;Apps are only affected if they embed untrusted content in iframes sandboxed with `allow-scripts allow-popups`. Apps that do not embed untrusted content in sandboxed iframes are not affected.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Use `setWindowOpenHandler` on the parent `WebContents` to deny or constrain popups opened from sandboxed frames, or do not apply `allow-popups` to sandboxed iframes that render untrusted content.&lt;/p&gt;
&lt;p&gt;### Fixed Versions&lt;/p&gt;
&lt;p&gt;* `43.0.0`
* `42.5.2`
* `41.10.4`&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, email us at [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&lt;/p&gt;
&lt;p&gt;Popups opened from a sandboxed iframe through a link (for example `target=&amp;#34;_blank&amp;#34;` or a middle-click) did not inherit the iframe&amp;#39;s HTML `sandbox` restrictions. Content that was meant to run sandboxed could open a popup with the embedding app&amp;#39;s full origin, gaining access to that origin&amp;#39;s cookies, storage, and same-origin scripting.&lt;/p&gt;
&lt;p&gt;Apps are only affected if they embed untrusted content in iframes sandboxed with `allow-scripts allow-popups`. Apps that do not embed untrusted content in sandboxed iframes are not affected.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Use `setWindowOpenHandler` on the parent `WebContents` to deny or constrain popups opened from sandboxed frames, or do not apply `allow-popups` to sandboxed iframes that render untrusted content.&lt;/p&gt;
&lt;p&gt;### Fixed Versions&lt;/p&gt;
&lt;p&gt;* `43.0.0`
* `42.5.2`
* `41.10.4`&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-hq2x-r82h-9wj4</guid>
    </item>
  </channel>
</rss>
