filament/filament security advisory

CVE-2026-77567: Filament: Multi-factor authentication (app) can be bypassed when recovery codes are enabled

CVE-2026-77567 is a high-severity authentication bypass vulnerability in the PHP package filament/filament (CVSS 8.1), published 24 August 2026. It is fixed in 4.12.0 and 5.7.0, one per release line; earlier versions on each line are affected. Exploiting it needs a low-privilege user account.

high 8.1 published 2026-08-24 · updated 2026-10-12

Affected versions: >= 4.0.0, < 4.12.0
>= 5.0.0, < 5.7.0
Fixed in: 4.12.0, 5.7.0
Newest release: 5.11.1
Severity: High · CVSS 8.1
Type: Authentication bypass
CWE-287
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your filament/filament version affected?

Run composer show filament/filament in your project, then enter the version. We check it against this and every other known filament/filament advisory.

Who can exploit CVE-2026-77567

Access: A normal, low-privilege user account in the app.

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Your app is only exposed if it uses the affected part of filament/filament. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-77567 in filament/filament

Find the installed version: composer show filament/filament. If you never required it yourself, composer why filament/filament shows which package pulls it in.
Update it: composer update filament/filament --with-all-dependencies. You need the fixed version for your release line (4.12.0 and 5.7.0).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "filament/filament": "^5.7.0" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-77567.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for authentication bypass issues while the upgrade waits. None of it replaces the fix.

Remove accounts you do not need and review what each role can do.
Put the admin area behind a VPN, IP allow-list or extra login until you upgrade.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-77567 advisory

Filament is a collection of full-stack components for accelerated Laravel development. Prior to versions 4.12.0 and 5.7.0, incorrect challenge-form required-field handling allows app-based multi-factor authentication to be bypassed when recovery codes are enabled. Email-based multi-factor authentication is not affected. This issue is fixed in versions 4.12.0 and 5.7.0.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-77567. Advisory title: “Filament: Multi-factor authentication (app) can be bypassed when recovery codes are enabled”.

References

GitHub advisory GHSA-52xp-w8hr-xv3c github.com
Fix commit 45534a6 github.com
Release v4.12.0 github.com
Release v5.7.0 github.com

Other filament/filament advisories

medium CVE-2026-104181: Filament: Multi-factor authentication (app) management actions do not require password reauthentication 2026-10-05
medium CVE-2026-84306: Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used 2026-09-01
low CVE-2026-84307: Filament: Password validity disclosure for accounts denied panel access on login page 2026-09-01
high CVE-2026-48505: Filament: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission 2026-06-25
medium CVE-2026-48500: Filament: Unauthenticated temporary file upload on auth pages 2026-06-23
medium CVE-2026-48166: Filament: Timing-based user enumeration on login page 2026-06-23

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.