CVE-2026-48505

Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission

Published Jun 22, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed

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.

Analysis

Technical impact

The flaw allows an attacker who has both a user's password and the recovery codes to submit the same code multiple times concurrently, creating more than one authenticated session per code. The issue stems from a race condition (CWE-362) and improper state handling (CWE-841). This defeats the intended single‑use guarantee of recovery codes, substantially extending the attacker's window of access.

Affected Systems

The vulnerability affects Filament versions 4.0.0 through 4.11.5 and 5.6.5. Only app‑based multi‑factor authentication with recovery codes enabled is impacted; email‑based MFA is unaffected.

Risk and Exploitability

The CVSS score of 7.4 indicates moderate‑to‑high severity. EPSS data is unavailable and the flaw is not listed in CISA KEV, so the current exploitation probability remains uncertain. An attacker must acquire the victim’s password and recovery codes and then submit them from multiple concurrent sessions, a path that is feasible through normal application usage once credentials are compromised.

Affected Products

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

filamentphp

filament

affected

Version	Status	Constraints
`>= 4.0.0, < 4.11.5`	affected	—
`>= 5.0.0, < 5.6.5`	affected	—

No data.

Vendor Product Versions

Filamentphp

Filament

Version	Status	Scheme	Platform
`[4.0.0,4.11.5)`	affected	semver	—
`[5.0.0,5.6.5)`	affected	semver	—

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

Update Filament to version 4.11.5 or 5.6.5, which contains the fix for the recovery‑code replay issue.
Revoke existing recovery codes and generate new ones after upgrading, ensuring that only fresh codes remain in use.
Encourage users to enable email‑based MFA or disable recovery codes entirely if they are not required for their workflow.

Generated by OpenCVE AI on June 22, 2026 at 23:25 UTC.

Tracking

Advisories

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

Metrics

No CVSS v4.0

Attack Vector Network

Attack Complexity High

Privileges Required None

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact None

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Exploit prediction score: < 1% (0.296% probability within 30 days)

Exploitation none

Automatable no

Technical Impact total

References

Link	Providers
https://github.com/filamentphp/filament/security/advisories/GHSA-mc5j-f6wx-h9qh

History

Jun 23, 2026 3:30 PM Scoring metrics updated View changes

Type	Values Removed	Values Added
Metrics		ssvc `{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}`

Jun 23, 2026 1:30 AM First appearance in the feed. Affected vendors updated View changes

Type	Values Removed	Values Added
First Time appeared		Filamentphp Filamentphp filament
Vendors & Products		Filamentphp Filamentphp filament

Jun 22, 2026 10:00 PM Description updated. Title updated. Weaknesses updated. Added references. Scoring metrics updated View changes

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		https://github.com/filamentphp/filament/security/advisories/GHSA-mc5j-f6wx-h9qh
Metrics		cvssV3_1 `{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}`

Subscriptions

Filamentphp Filament

Weaknesses

CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-841
Improper Enforcement of Behavioral Workflow