CVE-2026-84307: Filament: Password validity disclosure for accounts denied panel access on login page
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.5 and 5.7.5, packages/panels/src/Auth/Pages/Login.php presents the multi-factor authentication challenge before evaluating canAccessPanel(). For an account that canAccessPanel() denies, submitting the correct password renders the MFA challenge while an incorrect password returns the generic authentication failure, allowing an unauthenticated attacker to confirm whether a candidate password is valid for that account. When email-based MFA is configured, the correct-password path also sends a login code to the account holder. The issue applies only to accounts that have MFA enabled and are denied panel access. Authentication is not bypassed because canAccessPanel() still runs after the challenge, and no session is created. This issue is fixed in versions 4.12.5 and 5.7.5.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Filamentto a version that resolves this vulnerability.Fixed in 4.12.5 - Upgrade
Upgrade
Filamentto a version that resolves this vulnerability.Fixed in 5.7.5
Event History
Frequently Asked Questions
Which accounts are exposed to this password-validity oracle?
Only accounts that have MFA enabled and are denied access to the affected Filament panel by canAccessPanel() are exposed. Accounts that can access the panel, or denied accounts without MFA enabled, are not described as affected.
What must an attacker do to exploit the issue, and what can they learn?
An unauthenticated attacker submits password guesses for a denied account on the panel login page. A correct password causes the MFA challenge to appear, while an incorrect password produces a generic authentication failure, confirming whether a guessed password is valid.
Does exploitation allow an attacker to log in or create a session?
No. canAccessPanel() still runs after the MFA challenge, authentication is not bypassed, and no session is created.
Are there additional effects when email-based MFA is used?
Yes. For an affected denied account using email-based MFA, a correct password submission also sends a login code to the account holder.
Which versions contain the fix?
The issue is fixed in Filament versions 4.12.5 and 5.7.5. Affected versions are 4.0.0 through versions before 4.12.5, and version 5 releases before 5.7.5.