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

> Attackers can reuse MFA recovery codes via concurrent requests, gaining multiple authenticated sessions if they possess user credentials and recovery codes.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-mc5j-f6wx-h9qh

## What is CVE-2026-48505?

CVE-2026-48505 is a high-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-48505?

4 open source packages ship an affected version, including filament/filament.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 4.0.0 | 4.11.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.6.5 |

## How do I fix CVE-2026-48505?

Upgrade filament/filament to a fixed version for your release line: 4.11.5 or 5.6.5.

## Is CVE-2026-48505 being exploited?

There is no known exploitation of CVE-2026-48505 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48505 and fix it if it is affected.

What it is: CVE-2026-48505 is a high-severity vulnerability in filamentphp filament, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48505 in the wild and no public exploit code.

Affected packages and fixed versions:
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48505/ (Markdown: https://insights.sbomify.com/CVE-2026-48505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48505
- OSV: https://osv.dev/vulnerability/CVE-2026-48505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48505/
Summaries are generated and may contain mistakes; the official description above is the record.