Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission
Published 25 Jun 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- >=4.0.0 <4.11.5
- Fixed in
- 4.11.5
composer require filament/filament:^4.11.5- Affected
- >=5.0.0 <5.6.5
- Fixed in
- 5.6.5
composer require filament/filament:^5.6.5Details
A flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused via concurrent submission. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled.
If an attacker gains access to both the user's password and their recovery codes, they get two authenticated sessions per recovery code burned instead of one, or more if they batch the parallel submissions wider, materially extending the attacker's window of access compared to what the single-use guarantee implies.
Is GHSA-mc5j-f6wx-h9qh in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected filament/filament, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.