Summary
Filament: Multi-factor authentication (app) can be bypassed when recovery codes are enabled
Advisory details
A flaw in the challenge handling for app-based multi-factor authentication allows the second factor to be bypassed. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled.
References
- https://github.com/advisories/GHSA-52xp-w8hr-xv3c
- https://github.com/filamentphp/filament/security/advisories/GHSA-52xp-w8hr-xv3c
- https://nvd.nist.gov/vuln/detail/CVE-2026-77567
- https://github.com/filamentphp/filament/commit/45534a6f87f50ac6df3b43680bb33f8da9ef207b
- https://github.com/filamentphp/filament/releases/tag/v4.12.0
- https://github.com/filamentphp/filament/releases/tag/v5.7.0
Related vulnerabilities
All Supply chain →- MEDIUMCVE-2026-73840
OpenChoreo: Unauthenticated build/workflow trigger via git-provider confusion (webhook signature bypass)
- HIGHCVE-2026-62669
Grav: 2FA Bypass via 'login.regenerate2FASecret' - Secret Rotation During Pending Challenge
- MEDIUMCVE-2026-55678
arc has unauthenticated cluster node admission when `cluster.shared_secret` is unset
- HIGHCVE-2026-55761
Portainer has Unauthenticated Restore Endpoint that Allows Admin Takeover on Uninitialized Instances
- HIGHCVE-2026-55533
PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret
- MEDIUMCVE-2026-54176
Laravel Backpack CRUD: MyAccountController allows changing the login email without a current-password check