# CVE-2026-48166: Filament: Timing-based user enumeration on login page

> Unauthenticated attackers can enumerate registered email addresses via timing discrepancies on the login page of Filament applications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-5w46-g9pq-wh6f

## What is CVE-2026-48166?

CVE-2026-48166 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, the login page has an observable timing discrepancy that allows unauthenticated attackers to enumerate registered email addresses. The impact is limited to disclosing whether an account exists for a given email. This vulnerability is fixed in 4.11.5 and 5.6.5.

Weakness: CWE-208 (Observable Timing Discrepancy)

## Which versions are affected by CVE-2026-48166?

4 open source packages ship an affected version, including filament/filament.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |

## How do I fix CVE-2026-48166?

Upgrade filament/filament to a fixed version for your release line: 4.11.5 or 5.6.5.

## Is CVE-2026-48166 being exploited?

There is no known exploitation of CVE-2026-48166 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48166 and fix it if it is affected.

What it is: CVE-2026-48166 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48166 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48166/ (Markdown: https://insights.sbomify.com/CVE-2026-48166/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48166
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48166
- OSV: https://osv.dev/vulnerability/CVE-2026-48166

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48166/
Summaries are generated and may contain mistakes; the official description above is the record.