Quick answers
- Is CVE-2026-84307 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84307 being exploited in the wild.
- How severe is CVE-2026-84307?
- Low severity, with a CVSS score of 3.7, published 1 September 2026.
- Which products and versions are affected?
- Filament 4.0.0 to 4.12.4, 5.0.0 to 5.7.4; filament/filament (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.12.5.
- Is there a fix for CVE-2026-84307?
- Yes. filament/filament (Packagist): upgrade to 4.12.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84307 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-84307?
- Check whether you run Filament or filament/filament (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- filament/filament (Packagist): upgrade to 4.12.5 or later
composer require filament/filament:^4.12.5
Technical details
This information disclosure vulnerability exists in Filament's login flow when multi-factor authentication (MFA) is enabled. The root cause is an order-of-operations issue: the MFA challenge is presented before the `canAccessPanel()` authorization check. For accounts that fail `canAccessPanel()`, a correct password submission renders the MFA challenge, while an incorrect password returns a generic failure message. This allows an unauthenticated attacker to enumerate valid passwords for denied accounts via observable response discrepancy (CWE-204). When email-based MFA is in use, the attacker may also trigger MFA code delivery. The vulnerability has high attack complexity and requires knowledge of specific accounts with MFA enabled and denial policies. Authentication is not bypassed—the access control check still executes after challenge completion, preventing session creation for denied accounts. Patches are available in versions 4.12.5 and 5.7.5.
Affected products
- filamentphp Filament 4.0.0 to 4.12.4, 5.0.0 to 5.7.4
Identifiers
- CVE-2026-84307
- GHSA-xwpv-pqxp-5v36
Timeline
- 2026-08-17: disclosed: Published to GitHub Advisory Database
- 2026-09-01: advisory: Updated and reviewed on GitHub Advisory Database
- 2026: patched: Fixed in versions 4.12.5 and 5.7.5