<?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>Wed, 07 Oct 2026 00:03:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-380870</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-380870</link>
      <description>EUVD-2026-380870</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-380870</guid>
    </item>
    <item>
      <title>fkie_cve-2026-104181</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-104181</link>
      <description>&lt;p&gt;Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.13.3 and 5.8.3, app-based multi-factor authentication management actions do not consistently require confirmation of the current password. An attacker with access to an authenticated user session can set up app-based MFA and obtain recovery codes, or disable app-based MFA and regenerate recovery codes by supplying an existing app code or recovery code, without knowing the account password. Email-based MFA is not affected, and the issue does not independently permit an unauthenticated sign-in, but changing the app-MFA configuration may lock the legitimate user out. This issue is fixed in versions 4.13.3 and 5.8.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.13.3 and 5.8.3, app-based multi-factor authentication management actions do not consistently require confirmation of the current password. An attacker with access to an authenticated user session can set up app-based MFA and obtain recovery codes, or disable app-based MFA and regenerate recovery codes by supplying an existing app code or recovery code, without knowing the account password. Email-based MFA is not affected, and the issue does not independently permit an unauthenticated sign-in, but changing the app-MFA configuration may lock the legitimate user out. This issue is fixed in versions 4.13.3 and 5.8.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-104181</guid>
    </item>
    <item>
      <title>GHSA-7m6h-rg42-m449 — Filament: Multi-factor authentication (app) management actions do not require password reauthentication</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7m6h-rg42-m449</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: filament/filament&lt;/p&gt;
&lt;p&gt;App-based multi-factor authentication management actions did not consistently require the user to confirm their current password. In particular, an authenticated session could set up app-based MFA and obtain recovery codes without password reauthentication. Disabling app-based MFA and regenerating recovery codes also accepted an existing app code or recovery code without requiring the current password. This issue does not affect email-based MFA.&lt;/p&gt;
&lt;p&gt;If an attacker gains access to a user&amp;#39;s authenticated session, they could enable app-based MFA and obtain recovery codes without knowing the user&amp;#39;s password, changing the account&amp;#39;s MFA configuration and potentially locking the legitimate user out. This issue does not by itself allow an unauthenticated attacker to sign in.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: filament/filament&lt;/p&gt;
&lt;p&gt;App-based multi-factor authentication management actions did not consistently require the user to confirm their current password. In particular, an authenticated session could set up app-based MFA and obtain recovery codes without password reauthentication. Disabling app-based MFA and regenerating recovery codes also accepted an existing app code or recovery code without requiring the current password. This issue does not affect email-based MFA.&lt;/p&gt;
&lt;p&gt;If an attacker gains access to a user&amp;#39;s authenticated session, they could enable app-based MFA and obtain recovery codes without knowing the user&amp;#39;s password, changing the account&amp;#39;s MFA configuration and potentially locking the legitimate user out. This issue does not by itself allow an unauthenticated attacker to sign in.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7m6h-rg42-m449</guid>
    </item>
  </channel>
</rss>
