/

CVE-2026-77567

Severity:

HIGH RISK

(8.1)

Authentication Bypass (CWE-287) in Filament App MFA

CVE-2026-77567

Deferred

Vulnerability type

Category:

Authentication Bypass

CWE:

CWE-287

Impact:

Multi-Factor Authentication Bypass

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Filament versions before 4.12.0 and 5.7.0 contain incorrect required-field handling in app-based multi-factor authentication challenge forms. When recovery codes are enabled, an attacker may bypass the MFA challenge and access an account after passing the earlier authentication step; email-based MFA is not affected.

Affected context

The issue occurs in Filament applications using app-based multi-factor authentication with recovery codes enabled. It depends on the application's MFA challenge flow accepting an incompletely populated form because required-field validation is handled incorrectly. Email-based MFA deployments are outside the described affected behavior.

Exploit preconditions

  • Attack surface: Filament's application-based MFA challenge form
  • Required access: An account or session that reaches the MFA verification stage
  • Configuration condition: App-based MFA must be enabled with recovery codes available
  • Trigger point: Submission of an MFA challenge form with improperly handled required fields
  • Why exploitation is possible: Validation does not reliably require the expected challenge input before authentication proceeds

Why this happens

The underlying bug is improper enforcement of required authentication fields in an MFA challenge workflow. When the form-processing logic treats a missing or incomplete challenge value as valid, the authentication boundary can be crossed without successful second-factor verification. This behavior maps to CWE-287: Improper Authentication, because the application fails to correctly verify the identity claims required by its configured authentication mechanism.

Potential impact

  • An attacker may bypass app-based MFA for an affected account
  • Unauthorized access to protected application functionality could occur
  • Sensitive account or application data may be exposed
  • Attackers could perform actions using the privileges of the targeted account
  • Administrative or business-impacting operations could be carried out if a privileged account is affected

General mitigation guidance

Mitigation generally focuses on ensuring that every configured MFA challenge is mandatory and independently verified before access is granted.

Common defensive patterns include:

  • Applying server-side validation that rejects missing, empty, or malformed MFA challenge values
  • Ensuring recovery-code availability does not weaken enforcement of the primary app-based challenge
  • Making MFA flows fail closed when validation or challenge processing encounters an unexpected state
  • Limiting account and administrative privileges according to least-privilege principles
  • Monitoring and restricting recovery-code generation, viewing, and use
  • Using secure-by-default authentication components and maintaining supported security fixes through normal maintenance processes

How teams detect issues like this

Organizations can assess for this class of issue through:

  • Static analysis and code review of MFA form schemas, required-field rules, and server-side challenge validation
  • Tests that submit missing, empty, malformed, and duplicated challenge fields and confirm access is denied
  • Review of conditional branches involving recovery codes, alternate authentication methods, and challenge completion
  • Integration tests verifying that every successful login with app-based MFA includes a valid second-factor result
  • Policy enforcement requiring security-sensitive validation to occur on the server rather than relying only on client-side form state
  • Authentication logs that identify successful MFA completion without a corresponding valid challenge event

Sources

SourceLink
github.comgithub.com/filamentphp/filament/commit/45534a6f87f50ac6df3b43680bb33f8da9ef207b
github.comgithub.com/filamentphp/filament/releases/tag/v4.12.0
github.comgithub.com/filamentphp/filament/releases/tag/v5.7.0
github.comgithub.com/filamentphp/filament/security/advisories/GHSA-52xp-w8hr-xv3c

Frequently asked

questions

It may be exploitable through the application's normal authentication interface when an affected Filament MFA flow is reachable and the attacker has an account or session that reaches the challenge stage.

The described condition generally requires reaching the MFA challenge workflow, so an attacker may need valid primary authentication or another means of obtaining an eligible session. The exact requirement depends on the application's login design.

The described vulnerability specifically affects app-based MFA when recovery codes are enabled. Email-based MFA is not reported as affected by this issue.

Enforce required MFA fields with server-side, fail-closed validation and ensure that access is granted only after a valid challenge or explicitly authorized recovery-code path has been verified.

Find out what's already
exploitable in your codebase.