{"answers":{"affected":"4 open source packages ship an affected version, including filament/filament.","exploited":"There is no known exploitation of CVE-2026-77567 in the wild and no public exploit code.","fix":"Upgrade filament/filament to a fixed version for your release line: 4.12.0 or 5.7.0.","what":"CVE-2026-77567 is a high-severity authentication bypass vulnerability in filamentphp filament, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-77567 and fix it if it is affected.\n\nWhat it is: CVE-2026-77567 is a high-severity authentication bypass vulnerability in filamentphp filament, published on 24 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-77567 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- filament/filament (Packagist): affected from 4.0.0; fixed in 4.12.0\n- filament/filament (Packagist): affected from 4.0.0; fixed in 4.12.0\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.0\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77567/ (Markdown: https://insights.sbomify.com/CVE-2026-77567/index.md)","id":"CVE-2026-77567","markdown":"https://insights.sbomify.com/CVE-2026-77567/index.md","name":"CVE-2026-77567","record":{"aliases":["GHSA-52xp-w8hr-xv3c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Filament Laravel components","requires_auth":"low_privilege","summary":"Attackers can bypass app-based multi-factor authentication in Filament when recovery codes are enabled due to incorrect form handling.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"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.","ecosystems":["Packagist"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Filament: App-based MFA can be bypassed when recovery codes are enabled","id":"CVE-2026-77567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"Information disclosure in VeraCrypt","id":"CVE-2026-77572"},"packages":[{"ecosystem":"Packagist","fixed":["4.12.0"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-52xp-w8hr-xv3c"},{"ecosystem":"Packagist","fixed":["4.12.0"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-52xp-w8hr-xv3c"},{"ecosystem":"Packagist","fixed":["5.7.0"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-52xp-w8hr-xv3c"},{"ecosystem":"Packagist","fixed":["5.7.0"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-52xp-w8hr-xv3c"}],"prev":{"headline":"Talos Linux: Support bundle does not redact registry credentials","id":"CVE-2026-77564"},"products":["filament"],"published":"2026-08-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["filamentphp"]},"summary":"Attackers can bypass app-based multi-factor authentication in Filament when recovery codes are enabled due to incorrect form handling.","url":"https://insights.sbomify.com/CVE-2026-77567/"}