<?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, 12 Oct 2026 05:38:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55377 — Logto: Account Center MFA management step-up bypass via WebAuthn registration verification</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-55377</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; logto-io logto&lt;/p&gt;
&lt;p&gt;Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto&amp;#39;s Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; logto-io logto&lt;/p&gt;
&lt;p&gt;Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.41.0, Logto&amp;#39;s Account Center step-up check accepted any active verification record that belonged to the current user and had isVerified === true. A WebAuthn registration verification record for binding a new passkey could be created and verified with only an existing Account API bearer token, then sent in the logto-verification-id header and treated as identityVerified=true by Account Center routes, allowing MFA factor management without proving possession of an existing password, identifier, or MFA factor. This issue is fixed in version 1.41.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-55377</guid>
    </item>
  </channel>
</rss>
