<?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, 17 Nov 2026 04:51:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-391631</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391631</link>
      <description>EUVD-2026-391631</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391631</guid>
    </item>
    <item>
      <title>fkie_cve-2026-114607</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-114607</link>
      <description>&lt;p&gt;Better Auth is an authentication and authorization library for TypeScript. From 1.4.0-beta.18 until 1.7.7, deployments that enable Magic Link with storeToken set to plain, or with storeToken set to hashed and the global verification.storeIdentifier setting also set to hashed, enable a built-in social or Generic OAuth provider, and use account.storeStateStrategy set to database can accept an OAuth sign-in state value as a Magic Link token. These settings can cause Magic Link verification records and OAuth state to resolve to the same stored identifier, allowing an unauthenticated attacker to start OAuth sign-in for a known email address and redeem the returned state through Magic Link without controlling the mailbox or completing the provider callback. The attacker can obtain a normal session for an existing user, or create an account incorrectly marked as email verified when sign-up is enabled. This issue is fixed in version 1.7.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Better Auth is an authentication and authorization library for TypeScript. From 1.4.0-beta.18 until 1.7.7, deployments that enable Magic Link with storeToken set to plain, or with storeToken set to hashed and the global verification.storeIdentifier setting also set to hashed, enable a built-in social or Generic OAuth provider, and use account.storeStateStrategy set to database can accept an OAuth sign-in state value as a Magic Link token. These settings can cause Magic Link verification records and OAuth state to resolve to the same stored identifier, allowing an unauthenticated attacker to start OAuth sign-in for a known email address and redeem the returned state through Magic Link without controlling the mailbox or completing the provider callback. The attacker can obtain a normal session for an existing user, or create an account incorrectly marked as email verified when sign-up is enabled. This issue is fixed in version 1.7.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-114607</guid>
    </item>
    <item>
      <title>GHSA-965c-763c-88jm — better-auth: OAuth state can be used as a Magic Link to sign in as another user</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-965c-763c-88jm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: better-auth&lt;/p&gt;
&lt;p&gt;## Am I affected?&lt;/p&gt;
&lt;p&gt;You may be affected if you use `better-auth` from `1.4.0-beta.18` through versions before `1.7.7` with the Magic Link plugin and social or Generic OAuth sign-in.&lt;/p&gt;
&lt;p&gt;You are affected if **all** of these are true:&lt;/p&gt;
&lt;p&gt;- Magic Link is enabled with default `storeToken: &amp;#34;plain&amp;#34;`, or with `storeToken: &amp;#34;hashed&amp;#34;` and global `verification.storeIdentifier: &amp;#34;hashed&amp;#34;` (including a hashed default).
- At least one built-in social provider or Generic OAuth provider is enabled.
- OAuth state uses `account.storeStateStrategy: &amp;#34;database&amp;#34;`, the default when a database or secondary storage is configured.&lt;/p&gt;
&lt;p&gt;Cookie-backed state blocks this path, subject to the OAuth Proxy condition below. With custom hashers, confirm the flows cannot resolve to the same stored identifier.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Better Auth accepts an OAuth sign-in state value as a Magic Link token. An attacker can start an OAuth sign-in with any email address and use the returned state value to finish a Magic Link sign-in for that address. They never prove that they can read that email.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker who knows a user&amp;#39;s email address can get a normal session for that user, with all of that account&amp;#39;s permissions. They need no access to the mailbox, and they do not need to sign in with the OAuth provider or complete an OAuth callback.&lt;/p&gt;
&lt;p&gt;If Magic Link sign-up is enabled and no user has the email address, the attacker can instead create an account that Better Auth wrongly marks as email verified, and is sig…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: better-auth&lt;/p&gt;
&lt;p&gt;## Am I affected?&lt;/p&gt;
&lt;p&gt;You may be affected if you use `better-auth` from `1.4.0-beta.18` through versions before `1.7.7` with the Magic Link plugin and social or Generic OAuth sign-in.&lt;/p&gt;
&lt;p&gt;You are affected if **all** of these are true:&lt;/p&gt;
&lt;p&gt;- Magic Link is enabled with default `storeToken: &amp;#34;plain&amp;#34;`, or with `storeToken: &amp;#34;hashed&amp;#34;` and global `verification.storeIdentifier: &amp;#34;hashed&amp;#34;` (including a hashed default).
- At least one built-in social provider or Generic OAuth provider is enabled.
- OAuth state uses `account.storeStateStrategy: &amp;#34;database&amp;#34;`, the default when a database or secondary storage is configured.&lt;/p&gt;
&lt;p&gt;Cookie-backed state blocks this path, subject to the OAuth Proxy condition below. With custom hashers, confirm the flows cannot resolve to the same stored identifier.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;Better Auth accepts an OAuth sign-in state value as a Magic Link token. An attacker can start an OAuth sign-in with any email address and use the returned state value to finish a Magic Link sign-in for that address. They never prove that they can read that email.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An unauthenticated attacker who knows a user&amp;#39;s email address can get a normal session for that user, with all of that account&amp;#39;s permissions. They need no access to the mailbox, and they do not need to sign in with the OAuth provider or complete an OAuth callback.&lt;/p&gt;
&lt;p&gt;If Magic Link sign-up is enabled and no user has the email address, the attacker can instead create an account that Better Auth wrongly marks as email verified, and is sig…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-965c-763c-88jm</guid>
    </item>
  </channel>
</rss>
