Read the docs
TI-2026-57941 Aliases CVE-2026-84306GHSA-r3j6-gpjw-qfjr

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

Priority LOW 29CWE-294Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-294.

Summary

Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.6 and 5.7.6, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php uses AppAuthentication::verifyCode() with a used-code cache key derived from both the app authentication secret and the submitted TOTP code. This isolates the newest accepted timestep by code instead of by secret, allowing a previously issued app-based MFA code to be accepted after a newer code has already been used. Reuse of the exact same code was already prevented, but another code inside the accepted time window remained usable. An attacker who obtains the target account's password and one app-based MFA code can use that code for the remainder of the configured window, which is approximately four minutes with the default settings, even after the legitimate account holder logs in with a newer code. Email-based MFA is not affected. This issue is fixed in versions 4.12.6 and 5.7.6.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00448 39th percentileScored 2026-11-07
Fix Fixed filament (filamentphp): 4.12.6, 5.7.6filament/filament (Packagist): 4.12.6, 5.7.6

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
filamentphpfilament4.0.0 to before 4.12.6; 5.0.0 to before 5.7.64.12.6, 5.7.6Patch availableCNA
—filament/filament (Packagist)4.0.0 to before 4.12.64.12.6Patch availableGHSA-r3j6-gpjw-qfjr
—filament/filament (Packagist)5.0.0 to before 5.7.65.7.6Patch availableGHSA-r3j6-gpjw-qfjr
  • filament Vendorfilamentphp Affected 4.0.0 to before 4.12.6; 5.0.0 to before 5.7.6 Fixed in 4.12.6, 5.7.6 Patch available CNA
  • filament/filament (Packagist) Vendor— Affected 4.0.0 to before 4.12.6 Fixed in 4.12.6 Patch available GHSA-r3j6-gpjw-qfjr
  • filament/filament (Packagist) Vendor— Affected 5.0.0 to before 5.7.6 Fixed in 5.7.6 Patch available GHSA-r3j6-gpjw-qfjr

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:filamentphp:filament:*:*:*:*:*:*:*:*——filamentphp
  • cpe:2.3:a:filamentphp:filament:*:*:*:*:*:*:*:* Versions — — ·filamentphp

Remediation

  • Fix · CNA filament (filamentphp) Fixed in 4.12.6, 5.7.6
  • Fix · GHSA-r3j6-gpjw-qfjr filament/filament (Packagist) Fixed in 4.12.6 Advisory →
  • Fix · GHSA-r3j6-gpjw-qfjr filament/filament (Packagist) Fixed in 5.7.6 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-84306
  2. 2026-10-03 Alias added: GHSA-r3j6-gpjw-qfjr

References

  • TI-2024-34663 Exported files stored in default (`public`) filesystem if not reconfigured in filament CVSS 4.0LOW 2.3
  • TI-2026-54081 Filament: App-based MFA can be bypassed when recovery codes are enabled CVSS 3.1HIGH 8.1
  • TI-2025-41263 Filament's multi-factor authentication (app) recovery codes can be used multiple times CVSS 3.1HIGH 8.1
  • TI-2026-35861 Filament: Unauthenticated temporary file upload on auth pages CVSS 3.1MEDIUM 6.5
  • TI-2026-35865 Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission CVSS 3.1HIGH 7.4
  • TI-2026-39979 Filament: Disabled RichEditor field state can be used for XSS CVSS 3.1HIGH 7.6
See all 13 →

Sources