CVE-2026-104181 · GHSA-7m6h-rg42-m449
Filament: Multi-factor authentication (app) management actions do not require password reauthentication
- Risk score
- 43/100
- CVSS
- 5.4 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 1 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.13.3 and 5.8.3, app-based multi-factor authentication management actions do not consistently require confirmation of the current password. An attacker with access to an authenticated user session can set up app-ba…
- Affected
- filament/filament (composer) >= 4.0.0, <= 4.13.2; filament/filament (composer) >= 5.0.0, <= 5.8.2
- Fix
- Upgrade filament/filament to 4.13.3 or 5.8.3 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 5.4 medium
- On your watchlist: Composer
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| filament/filament | composer | >= 4.0.0, <= 4.13.2 | 4.13.3 |
| filament/filament | composer | >= 5.0.0, <= 5.8.2 | 5.8.3 |
References
- https://github.com/advisories/GHSA-7m6h-rg42-m449
- https://github.com/filamentphp/filament/security/advisories/GHSA-7m6h-rg42-m449
- https://nvd.nist.gov/vuln/detail/CVE-2026-104181
- https://github.com/filamentphp/filament/pull/20522
- https://github.com/filamentphp/filament/commit/6d4dae6d7a94ce5aefd7ed4dc836acb0e6b71bb1
- https://github.com/filamentphp/filament/releases/tag/v4.13.3
- https://github.com/filamentphp/filament/releases/tag/v5.8.3
- https://github.com/advisories/GHSA-7m6h-rg42-m449
Original description
Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.13.3 and 5.8.3, app-based multi-factor authentication management actions do not consistently require confirmation of the current password. An attacker with access to an authenticated user session can set up app-based MFA and obtain recovery codes, or disable app-based MFA and regenerate recovery codes by supplying an existing app code or recovery code, without knowing the account password. Email-based MFA is not affected, and the issue does not independently permit an unauthenticated sign-in, but changing the app-MFA configuration may lock the legitimate user out. This issue is fixed in versions 4.13.3 and 5.8.3.
Last activity 1 Oct 2026. Patch Forecast updates every hour.