dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-48505

HIGH · 7.4 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Filament's MFA recovery code handling contains a race condition where concurrent submission of the same recovery code bypasses the single-use guarantee. The application validates the code's validity but does not atomically mark it as consumed, allowing parallel requests to each receive a valid authentication session before the code is invalidated.

MitigationUpgrade Filament to version 4.11.5 or 5.6.5 or later where the recovery code consumption is properly atomic. If immediate upgrade is not possible, consider disabling recovery codes for app-based MFA as a temporary mitigation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Filament version
    Run 'composer show filament/filament' or inspect your composer.lock file for the filament/filament package version number
    Affected if Version is earlier than 4.11.5 for the 4.x branch or between 5.0.0 and 5.6.4 for the 5.x branch
  2. Verify Filament two-factor authentication is enabled
    Check your Filament authentication configuration for two-factor authentication settings in config/filament.php or in the auth configuration
    Affected if Filament MFA feature is enabled in the application
  3. Confirm recovery codes are configured as an MFA backup
    Examine whether users have recovery codes generated and enabled - check the Filament user model for two_factor_columns or recovery codes storage
    Affected if Recovery codes are available as an MFA recovery method in your Filament installation

If your Filament version is below 4.11.5 or between 5.0.0 and 5.6.4 AND you have Filament MFA with recovery codes enabled, the race condition vulnerability is present in your environment

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Filament to version 4.11.5 or 5.6.5 or later where the recovery code consumption is properly atomic. If immediate upgrade is not possible, consider disabling recovery codes for app-based MFA as a temporary mitigation.

Recommended fix High confidence

Filament v4.11.5 or v5.6.5 (depending on your current major version)

  1. Identify the currently installed Filament version using composer show filament/filament or your composer.json
  2. Determine which major version branch you are on (v4.x or v5.x)
  3. Run composer require filament/filament:^4.11.5 to upgrade to the v4 fixed release, or composer require filament/filament:^5.6.5 to upgrade to the v5 fixed release
  4. Run composer update filament/filament to apply the changes
  5. Verify the upgrade was successful by checking the installed version
  6. Test MFA recovery code functionality to confirm the race condition is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48505 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-48505 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data