<?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>Thu, 05 Nov 2026 17:18:49 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-110826</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-110826</link>
      <description>&lt;p&gt;Improper Session Invalidation after Authentication Credential Change vulnerability in team-alembic ash_authentication allows an attacker holding a victim&amp;#39;s session token to stay signed in after the victim resets or changes their password.&lt;/p&gt;
&lt;p&gt;With apply_on_password_change? true, AshAuthentication.AddOn.LogOutEverywhere.Transformer adds OnPasswordChange to update actions as a global change guarded by where: changing(hashed_password). That condition is evaluated before the action&amp;#39;s before_action hooks run, but AshAuthentication.Strategy.Password.HashPasswordChange sets the new hash in a before_action hook, so for every non-atomic password change the condition is false and the user&amp;#39;s stored tokens are not revoked. The generated password reset action and the installer&amp;#39;s change_password action are both non-atomic.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication: from 4.5.0 before 4.15.1 and from 5.0.0-rc.0 before 5.0.0-rc.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Session Invalidation after Authentication Credential Change vulnerability in team-alembic ash_authentication allows an attacker holding a victim&amp;#39;s session token to stay signed in after the victim resets or changes their password.&lt;/p&gt;
&lt;p&gt;With apply_on_password_change? true, AshAuthentication.AddOn.LogOutEverywhere.Transformer adds OnPasswordChange to update actions as a global change guarded by where: changing(hashed_password). That condition is evaluated before the action&amp;#39;s before_action hooks run, but AshAuthentication.Strategy.Password.HashPasswordChange sets the new hash in a before_action hook, so for every non-atomic password change the condition is false and the user&amp;#39;s stored tokens are not revoked. The generated password reset action and the installer&amp;#39;s change_password action are both non-atomic.&lt;/p&gt;
&lt;p&gt;This issue affects ash_authentication: from 4.5.0 before 4.15.1 and from 5.0.0-rc.0 before 5.0.0-rc.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-110826</guid>
    </item>
  </channel>
</rss>
