# CVE-2026-84306: Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used

> Attackers with stolen credentials and one MFA code can bypass multi-factor authentication by reusing valid codes within the time window.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/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:** 1 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-r3j6-gpjw-qfjr

## What is CVE-2026-84306?

CVE-2026-84306 is a medium-severity authentication bypass vulnerability in filamentphp filament, published on 1 Sep 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.12.6 and 5.7.6, packages/panels/src/Auth/MultiFactor/App/AppAuthentication.php uses AppAuthentication::verifyCode() with a used-code cache key derived from both the app authentication secret and the submitted TOTP code. This isolates the newest accepted timestep by code instead of by secret, allowing a previously issued app-based MFA code to be accepted after a newer code has already been used. Reuse of the exact same code was already prevented, but another code inside the accepted time window remained usable. An attacker who obtains the target account's password and one app-based MFA code can use that code for the remainder of the configured window, which is approximately four minutes with the default settings, even after the legitimate account holder logs in with a newer code. Email-based MFA is not affected. This issue is fixed in versions 4.12.6 and 5.7.6.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `filament/filament` | Packagist | From 4.0.0 | 4.12.6 |
| `filament/filament` | Packagist | From 4.0.0 | 4.12.6 |
| `filament/filament` | Packagist | From 5.0.0 | 5.7.6 |
| `filament/filament` | Packagist | From 5.0.0 | 5.7.6 |

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

Upgrade filament/filament to a fixed version for your release line: 4.12.6 or 5.7.6.

## Is CVE-2026-84306 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84306 is a medium-severity authentication bypass vulnerability in filamentphp filament, published on 1 Sep 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-84306 in the wild and no public exploit code.

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

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-84306/ (Markdown: https://insights.sbomify.com/CVE-2026-84306/index.md)
```

## Sources

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

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