<?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>Wed, 07 Oct 2026 08:07:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54673 — electron-updater: Cross-origin redirect leaks `PRIVATE-TOKEN` and mixed-case `Authorization` credentials in `builder-ut…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-54673</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; electron-userland electron-builder, electron-userland builder-util-runtime&lt;/p&gt;
&lt;p&gt;electron-updater allows for automatic updates for Electron apps. Prior to 9.7.0, the HTTP redirect handler (HttpExecutor.prepareRedirectUrlOptions) only stripped a credential header whose key string matched exactly lowercase &amp;#34;authorization&amp;#34;, exposing credentials. Other credential-bearing headers — most notably PRIVATE-TOKEN (used by GitLab&amp;#39;s personal access token flow) and mixed-case Authorization (used by GitLab&amp;#39;s Bearer/OAuth flow) — were not stripped and could be forwarded to an attacker-controlled cross-origin redirect destination. This issue has been fixed in version 9.7.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; electron-userland electron-builder, electron-userland builder-util-runtime&lt;/p&gt;
&lt;p&gt;electron-updater allows for automatic updates for Electron apps. Prior to 9.7.0, the HTTP redirect handler (HttpExecutor.prepareRedirectUrlOptions) only stripped a credential header whose key string matched exactly lowercase &amp;#34;authorization&amp;#34;, exposing credentials. Other credential-bearing headers — most notably PRIVATE-TOKEN (used by GitLab&amp;#39;s personal access token flow) and mixed-case Authorization (used by GitLab&amp;#39;s Bearer/OAuth flow) — were not stripped and could be forwarded to an attacker-controlled cross-origin redirect destination. This issue has been fixed in version 9.7.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-54673</guid>
    </item>
  </channel>
</rss>
