<?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 19:12:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55186 — Silverstripe MFA: Can bypass MFA during password reset flow</title>
      <link>https://db.gcve.eu/vuln/cve-2026-55186</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; silverstripe-mfa&lt;/p&gt;
&lt;p&gt;Silverstripe MFA provides multi-factor authentication for Silverstripe CMS. Prior to 6.0.0, the CMS 5 password reset flow can issue a logged-in session after a user changes a password but before the user&amp;#39;s configured multi-factor authentication challenge is completed. An attacker with access to the user&amp;#39;s email account can follow the reset flow and bypass the additional authentication factor. CMS 6 is not affected. This issue is fixed in version 6.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; silverstripe-mfa&lt;/p&gt;
&lt;p&gt;Silverstripe MFA provides multi-factor authentication for Silverstripe CMS. Prior to 6.0.0, the CMS 5 password reset flow can issue a logged-in session after a user changes a password but before the user&amp;#39;s configured multi-factor authentication challenge is completed. An attacker with access to the user&amp;#39;s email account can follow the reset flow and bypass the additional authentication factor. CMS 6 is not affected. This issue is fixed in version 6.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-55186</guid>
    </item>
  </channel>
</rss>
