Résumé
Filament: Multi-factor authentication (app) can be bypassed when recovery codes are enabled
Détails de l’avis
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.
Références
- 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
Vulnérabilités liées
Tout Supply chain →- HIGHCVE-2026-84312
Nginx UI: Casdoor SSO callback uses a constant `state` parameter (login CSRF)
- HIGHCVE-2026-84313
Nginx UI: TOTP / passkey enrolment requires no re-authentication, enabling persistent account takeover
- HIGHCVE-2026-62367
Vikunja: OIDC email-fallback account linking ignores email_verified, enabling local-account takeover
- HIGHGHSA-68w4-83fh-f2w8
pyload-ng: getUserData/get_userdata exposed at Perms.ANY allow any authenticated account to brute-force the administrator password
- HIGHCVE-2026-107808
Nginx UI: Authentication bypass: password login does not enforce a passkey-only second factor (2FA bypass)
- HIGHGHSA-r44w-v6gf-x3p6
pyLoad has an authentication bypass in API key validation (check_apikey cache)