CVE-2026-77567 filamentphp CVE debrief

Who should care

Defenders responsible for Laravel applications using Filament should assess exposure and prioritize patching to prevent potential authentication bypasses. This includes reviewing multi-factor authentication configurations and recovery code settings, verifying and applying patches to Filament versions 4.12.0 or 5.7.0, and assessing exposure in their Laravel applications.

Why it matters

CVE-2026-77567 is a high-severity vulnerability in Filament that allows app-based multi-factor authentication to be bypassed when recovery codes are enabled. Defenders should prioritize verifying and applying patches, assessing exposure, and reviewing multi-factor authentication configurations.

• Potential authentication bypass in app-based multi-factor authentication
• Verification of patch application and configuration review required
• Possible impact on security posture if recovery codes are enabled

Technical summary

The vulnerability in Filament allows app-based multi-factor authentication to be bypassed when recovery codes are enabled. This issue is fixed in Filament versions 4.12.0 and 5.7.0. Email-based multi-factor authentication is not affected. The CVE record and NVD entry provide details on the vulnerability, its impact, and fixed versions. However, additional information on affected deployments, exploitation attempts, or specific attack vectors is limited. Defenders should prioritize verifying and applying the patches to Filament versions 4.12.0 and 5.7.0, assessing exposure in their Laravel applications, and reviewing multi-factor authentication configurations.

Defensive priority

Defenders should prioritize verifying and applying the patches to Filament versions 4.12.0 and 5.7.0, assessing exposure in their Laravel applications, and reviewing multi-factor authentication configurations.

Recommended defensive actions

• Verify and apply patches to Filament versions 4.12.0 or 5.7.0
• Assess exposure in Laravel applications using Filament
• Review multi-factor authentication configurations and recovery code settings
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and fixed versions. However, additional information on affected deployments, exploitation attempts, or specific attack vectors is limited.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.