Is filament/filament 4.13 vulnerable?
Composer · 5 releases from 4.13.0 to 4.13.4 · latest filament/filament is 5.11.4 · checked 18 Nov 2026
No known advisories in the last release
filament/filament 4.13.4, the last 4.13 release, has no known advisories. 1 advisory affects earlier 4.13.x releases, so update to 4.13.4.
composer require filament/filament:^4.13.4Is your project on an affected filament/filament?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 4.13.x, affecting earlier releases
Filament: Multi-factor authentication (app) management actions do not require password reauthentication
- Affected
- >=4.0.0 <4.13.3 · >=5.0.0 <5.8.3
- Fixed in
- 4.13.3, 5.8.3
Every filament/filament 4.13.x release
Affected: 4.13.0 to 4.13.2. 4.13.3 and later are not affected. Latest filament/filament: 5.11.4.
| Version | Known advisories |
|---|---|
| filament/filament 4.13.4 | None |
| filament/filament 4.13.3 | None |
| filament/filament 4.13.2 | CVE-2026-104181 |
| filament/filament 4.13.1 | CVE-2026-104181 |
| filament/filament 4.13.0 | CVE-2026-104181 |
Which of your client projects are still on filament/filament 4.13?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact filament/filament version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other filament/filament versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.