<?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>Tue, 29 Sep 2026 09:18:59 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-81637</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-81637</link>
      <description>&lt;p&gt;Insufficient Session Expiration vulnerability in team-alembic AshAuthentication allows an attacker who obtains a victim&amp;#39;s OAuth2 state value to replay the callback and sign that victim into an attacker-controlled account.&lt;/p&gt;
&lt;p&gt;AshAuthentication.Strategy.OAuth2.Plug.callback/2 clears the stored session_params through a rebinding step inside its with chain, conn &amp;lt;- delete_session(conn, session_key). Elixir evaluates the else block in the scope enclosing the with, so every failure path (the provider returning ?error=access_denied, an invalid code, a token-exchange error, or a registration or sign-in failure) reaches store_authentication_result/2 holding the original connection and the session entry is never removed. The value the module&amp;#39;s own comment describes as protection against a CSRF-related attack is therefore consumed only when authentication succeeds, and survives a cancelled or failed attempt until the next request phase or session expiry.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication: from 0.6.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Insufficient Session Expiration vulnerability in team-alembic AshAuthentication allows an attacker who obtains a victim&amp;#39;s OAuth2 state value to replay the callback and sign that victim into an attacker-controlled account.&lt;/p&gt;
&lt;p&gt;AshAuthentication.Strategy.OAuth2.Plug.callback/2 clears the stored session_params through a rebinding step inside its with chain, conn &amp;lt;- delete_session(conn, session_key). Elixir evaluates the else block in the scope enclosing the with, so every failure path (the provider returning ?error=access_denied, an invalid code, a token-exchange error, or a registration or sign-in failure) reaches store_authentication_result/2 holding the original connection and the session entry is never removed. The value the module&amp;#39;s own comment describes as protection against a CSRF-related attack is therefore consumed only when authentication succeeds, and survives a cancelled or failed attempt until the next request phase or session expiry.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication: from 0.6.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-81637</guid>
    </item>
  </channel>
</rss>
