Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mc5j-f6wx-h9qh | Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission |
Tue, 23 Jun 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 23 Jun 2026 01:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Filamentphp
Filamentphp filament |
|
| Vendors & Products |
Filamentphp
Filamentphp filament |
Mon, 22 Jun 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, 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. This vulnerability is fixed in 4.11.5 and 5.6.5. | |
| Title | Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission | |
| Weaknesses | CWE-362 CWE-841 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-23T14:28:42.081Z
Reserved: 2026-05-21T16:18:10.618Z
Link: CVE-2026-48505
Updated: 2026-06-23T14:28:37.372Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-23T01:15:16Z
Github GHSA