<?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>Mon, 05 Oct 2026 23:10:14 +0000</lastBuildDate>
    <item>
      <title>BIT-parse-2026-27804 — Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter</title>
      <link>https://cve.radiocsirt.org/vuln/bit-parse-2026-27804</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.3.1, an unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. The fix in versions 8.6.3 and 9.3.1 hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: parse&lt;/p&gt;
&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.3.1, an unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. The fix in versions 8.6.3 and 9.3.1 hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-parse-2026-27804</guid>
    </item>
    <item>
      <title>EUVD-2026-271706</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-271706</link>
      <description>EUVD-2026-271706</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-271706</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27804</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27804</link>
      <description>&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.1.1-alpha.4, an unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. The fix in versions 8.6.3 and 9.1.1-alpha.4 hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.3 and 9.1.1-alpha.4, an unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected. The fix in versions 8.6.3 and 9.1.1-alpha.4 hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs. As a workaround, dsable Google authentication until upgrading is possible.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27804</guid>
    </item>
    <item>
      <title>GHSA-4q3h-vp4r-prv2 — Parse Server: Account takeover via JWT algorithm confusion in Google auth adapter</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4q3h-vp4r-prv2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable Google authentication until you can upgrade.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- GitHub advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4q3h-vp4r-prv2
- Fixed in Parse Server 9.3.1-alpha.4: https://github.com/parse-community/parse-server/releases/tag/9.3.1-alpha.4
- Fixed in Parse Server 8.6.3: https://github.com/parse-community/parse-server/releases/tag/8.6.3&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: parse-server&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker can forge a Google authentication token with `alg: &amp;#34;none&amp;#34;` to log in as any user linked to a Google account, without knowing their credentials. All deployments with Google authentication enabled are affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix hardcodes the expected `RS256` algorithm instead of trusting the JWT header, and replaces the Google adapter&amp;#39;s custom key fetcher with `jwks-rsa` which rejects unknown key IDs.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Disable Google authentication until you can upgrade.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- GitHub advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-4q3h-vp4r-prv2
- Fixed in Parse Server 9.3.1-alpha.4: https://github.com/parse-community/parse-server/releases/tag/9.3.1-alpha.4
- Fixed in Parse Server 8.6.3: https://github.com/parse-community/parse-server/releases/tag/8.6.3&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4q3h-vp4r-prv2</guid>
    </item>
  </channel>
</rss>
