# CVE-2026-84307: Filament: Password validity disclosure for accounts denied panel access on login page

> An attacker can verify valid passwords for accounts denied panel access by observing MFA challenge responses, leaking credential validity.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 2 Sep 2026
- **Also known as:** GHSA-xwpv-pqxp-5v36

## What is CVE-2026-84307?

CVE-2026-84307 is a low-severity 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.5 and 5.7.5, packages/panels/src/Auth/Pages/Login.php presents the multi-factor authentication challenge before evaluating canAccessPanel(). For an account that canAccessPanel() denies, submitting the correct password renders the MFA challenge while an incorrect password returns the generic authentication failure, allowing an unauthenticated attacker to confirm whether a candidate password is valid for that account. When email-based MFA is configured, the correct-password path also sends a login code to the account holder. The issue applies only to accounts that have MFA enabled and are denied panel access. Authentication is not bypassed because canAccessPanel() still runs after the challenge, and no session is created. This issue is fixed in versions 4.12.5 and 5.7.5.

Weakness: CWE-204 (Observable Response Discrepancy)

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

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.5 |
| `filament/filament` | Packagist | From 4.0.0 | 4.12.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.7.5 |
| `filament/filament` | Packagist | From 5.0.0 | 5.7.5 |

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

Upgrade filament/filament to a fixed version for your release line: 4.12.5 or 5.7.5.

## Is CVE-2026-84307 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84307 is a low-severity 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-84307 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.5
- filament/filament (Packagist): affected from 4.0.0; fixed in 4.12.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.5
- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.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-84307/ (Markdown: https://insights.sbomify.com/CVE-2026-84307/index.md)
```

## Sources

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

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