Skip to main content
Vulnerability Database/CVE-2026-104181

CVE-2026-104181: Filament Laravel Auth Bypass Vulnerability

CVE-2026-104181 is an authentication bypass flaw in Filament Laravel that allows attackers with session access to manipulate MFA settings without password confirmation. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104181 Overview

CVE-2026-104181 affects Filament, a collection of full-stack components for accelerated Laravel development. The vulnerability resides in app-based multi-factor authentication (MFA) management actions that do not consistently require confirmation of the current account 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 only an existing app code or recovery code. Email-based MFA is not affected, and the flaw does not independently permit unauthenticated sign-in. However, modifying app-MFA configuration may lock the legitimate user out. The issue is classified under [CWE-306: Missing Authentication for Critical Function].

Critical Impact

An attacker with an authenticated session can hijack or disable app-based MFA without knowing the account password, potentially locking out the legitimate user and persisting access via attacker-controlled recovery codes.

Affected Products

  • Filament versions 4.0.0 through 4.13.2
  • Filament versions 5.0.0 through 5.8.2
  • Laravel applications using Filament panels with app-based MFA enabled

Discovery Timeline

  • 2026-10-01 - CVE-2026-104181 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-104181

Vulnerability Analysis

The vulnerability affects the MFA management workflow in Filament's panels package. When a user manages app-based MFA—setup, disable, or regenerate recovery codes—the application accepts proof of possession (a valid app code or recovery code) in place of proof of knowledge (the current password). The two factors are not combined, so an attacker who has only hijacked a session can rebind the MFA configuration to a device under their control.

Because recovery codes are regenerated during these actions, the legitimate account owner loses their previously stored recovery codes. Combined with a disabled or rotated authenticator secret, this creates a lockout condition while preserving attacker access through the newly issued credentials.

Root Cause

The root cause is missing authentication for a critical function [CWE-306]. The MFA disable and recovery-code regeneration forms accept a code-only path, with the password field either absent or marked optional. The patch introduces a required password form field across these actions and updates localization labels from "or enter the current password" to "enter the current password", making password confirmation mandatory.

Attack Vector

Exploitation requires an authenticated session, obtained via session fixation, cookie theft, cross-site scripting, or a shared workstation. Once authenticated, the attacker navigates to the account's MFA settings and either disables app-based MFA or regenerates recovery codes by supplying a currently valid app code or an existing recovery code. The attacker does not need the account password at any point in this flow.

php
// Patch excerpt — disable.php (localization)
// Source: https://github.com/filamentphp/filament/commit/6d4dae6d7a94ce5aefd7ed4dc836acb0e6b71bb1

'form' => [
+    'password' => [
+        'label' => 'كلمة المرور الحالية',
+        'validation_attribute' => 'كلمة المرور الحالية',
+    ],

    'code' => [
        // ...
    ],
],

// Patch excerpt — regenerate-recovery-codes.php
'password' => [
-    'label' => 'أو أدخل كلمة المرور الحالية',  // "or enter the current password"
+    'label' => 'أدخل كلمة المرور الحالية',     // "enter the current password"
    'validation_attribute' => 'كلمة المرور',
],

The patch adds a mandatory current-password field to the disable action and removes the "or" conjunction from the regenerate-recovery-codes action, enforcing password confirmation. See the Filament security advisory GHSA-7m6h-rg42-m449 for full details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-104181

Indicators of Compromise

  • Successful POST requests to MFA management routes under the Filament panel path (for example, /admin/multi-factor/app/disable or /admin/multi-factor/app/regenerate-recovery-codes) without a corresponding password-confirmation challenge in session logs.
  • User account audit entries showing MFA disable, re-enroll, or recovery-code regeneration events clustered in time with no preceding password prompt.
  • End-user support tickets reporting unexpected MFA reset or inability to log in using previously saved recovery codes.

Detection Strategies

  • Correlate web server access logs for requests to Filament MFA endpoints against application authentication logs to confirm that password re-authentication occurred immediately before the state change.
  • Review Laravel application logs and audit tables for multi_factor_app_authentication_secret or recovery-code column mutations tied to users who did not initiate a profile change.
  • Hunt for session reuse patterns: the same session ID performing MFA configuration changes from a different IP address or user-agent than the original sign-in.

Monitoring Recommendations

  • Alert on any update to MFA fields on the users table (or Filament's equivalent) outside of a documented self-service or admin-driven workflow.
  • Monitor for bursts of recovery-code regeneration events across multiple accounts, which can indicate a compromised session store or stolen cookies.
  • Enable Laravel audit logging on the Filament authentication guard and ship events to a centralized log platform for retention and correlation.

How to Mitigate CVE-2026-104181

Immediate Actions Required

  • Upgrade Filament to version 4.13.3 (for the 4.x branch) or 5.8.3 (for the 5.x branch) immediately.
  • Invalidate all active user sessions after upgrade to force re-authentication through the patched flow.
  • Audit recent MFA configuration changes and notify any affected users to re-enroll their authenticator and store new recovery codes.

Patch Information

The fix is published in Filament release v4.13.3 and Filament release v5.8.3. The code change is tracked in pull request #20522 and merged in commit 6d4dae6. The patch adds a required password form field to the app-MFA disable, setup, and regenerate-recovery-codes actions.

Workarounds

  • Temporarily disable the app-based MFA management actions in the Filament panel until the upgrade is applied, leaving email-based MFA as the enrolled factor where supported.
  • Enforce short session lifetimes and require password re-authentication on sensitive routes using Laravel's password.confirm middleware on custom MFA controllers.
  • Restrict access to the Filament admin or user panel from trusted networks only, reducing the window for session theft to be used against MFA settings.
bash
# Composer upgrade — Filament 4.x branch
composer require filament/filament:^4.13.3 --update-with-dependencies

# Composer upgrade — Filament 5.x branch
composer require filament/filament:^5.8.3 --update-with-dependencies

# Invalidate active sessions after upgrade
php artisan session:table   # if using database driver
php artisan cache:clear
php artisan auth:clear-resets

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.