Quick answers
- Is CVE-2026-48166 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48166 being exploited in the wild.
- How severe is CVE-2026-48166?
- Medium severity, with a CVSS score of 5.3, published 22 June 2026.
- Which products and versions are affected?
- Filament >= 4.0.0, < 4.11.5; >= 5.0.0, < 5.6.5; filament/filament (Packagist) ECOSYSTEM:introduced=4.0.0,fixed=4.11.5.
- Is there a fix for CVE-2026-48166?
- Yes. filament/filament (Packagist): upgrade to 4.11.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48166 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-48166?
- 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.11.5 or later
composer require filament/filament:^4.11.5
Technical details
A timing-based user enumeration vulnerability (CWE-208) exists in the Filament login component. The root cause is an observable timing discrepancy during the authentication process, where the server's response time varies depending on whether a provided email address exists in the database. An unauthenticated remote attacker can exploit this by sending multiple login requests and analyzing response times to identify valid user accounts. This issue is resolved in versions 4.11.5 and 5.6.5.
Affected products
- filamentphp filament >= 4.0.0, <= 4.11.4
- filamentphp filament >= 5.0.0, <= 5.6.4
Identifiers
- CVE-2026-48166
- GHSA-5w46-g9pq-wh6f
Timeline
- 2026-05-23: disclosed
- 2026-06-22: advisory: NVD publication date
- 2026-06-23: patched: GitHub Advisory published and reviewed