Skip to content
Applications

CVE-2026-77567

8.1
High
EPSS 0.30%Patch availableAug 25, 2026

Authentication bypass in Filament app-based MFA when recovery codes enabled.

common questions

Is CVE-2026-77567 being exploited?

Not confirmed. CVE-2026-77567 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-77567?

CVE-2026-77567 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77567?

Yes. A fix has been recorded for CVE-2026-77567. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77567 affect?

CVE-2026-77567 affects Filament < 4.12.0, Filament < 5.7.0, Laravel apps using Filament with app-based MFA and recovery codes enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77567?

Upgrade to Filament 4.12.0/5.7.0 and audit MFA/recovery-code settings

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Filament < 4.12.0Filament < 5.7.0Laravel apps using Filament with app-based MFA and recovery codes enabled
impact

Attackers can bypass app-based MFA when recovery codes are enabled, enabling account takeover of affected Laravel apps.

action required

Immediate action required

affected versions
filamentphp filament
  • affected>= 4.0.0 and < 4.12.0
  • affected>= 5.0.0 and < 5.7.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free