cve.bz

CVE-2026-48505 filamentphp filament: Race Condition

7.4 highEPSS 0.3%Fix available

High (7.4) in filamentphp filament. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in filament/filament 4.11.5, 5.6.5.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-06-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
CWE-841 Improper Enforcement of Behavioral Workflow
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • filament/filament (Packagist): fixed in 4.11.5, 5.6.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-48505 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48505?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48505?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48505 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
filamentphp filament>= 4.0.0, < 4.11.5
filamentphp filament>= 5.0.0, < 5.6.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mc5j-f6wx-h9qhPackagistfilament/filament>=4.0.0 <4.11.54.11.5
GHSA-mc5j-f6wx-h9qhPackagistfilament/filament>=5.0.0 <5.6.55.6.5

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON