MediumGHSA-r3j6-gpjw-qfjrCVE-2026-84306

Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used

Published 1 Sept 2026 · Updated 1 Sept 2026

Affected packages

Affected
>=4.0.0 <4.12.6
Fixed in
4.12.6
Update to the fixed version for your release line, for example:composer require filament/filament:^4.12.6
Affected
>=5.0.0 <5.7.6
Fixed in
5.7.6
Update to the fixed version for your release line, for example:composer require filament/filament:^5.7.6

Details

A flaw in the handling of one-time codes for app-based multi-factor authentication allows a previously issued code to be used after a newer code has already been accepted. This issue does not affect email-based MFA. Submitting the exact same code twice was already prevented, but any other code within the accepted time window was not.

If an attacker gains access to both the user's password and a single one-time code, that code stays usable for the remainder of its time window, which is around four minutes on the default settings, including after the legitimate user has already logged in with a newer code.

Is GHSA-r3j6-gpjw-qfjr 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.