{"answers":{"affected":"4 open source packages ship an affected version, including filament/filament.","exploited":"There is no known exploitation of CVE-2026-84307 in the wild and no public exploit code.","fix":"Upgrade filament/filament to a fixed version for your release line: 4.12.5 or 5.7.5.","what":"CVE-2026-84307 is a low-severity vulnerability in filamentphp filament, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-84307 and fix it if it is affected.\n\nWhat it is: CVE-2026-84307 is a low-severity vulnerability in filamentphp filament, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84307 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.5\n- filament/filament (Packagist): affected from 4.0.0; fixed in 4.12.5\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.5\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.7.5\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-84307/ (Markdown: https://insights.sbomify.com/CVE-2026-84307/index.md)","id":"CVE-2026-84307","markdown":"https://insights.sbomify.com/CVE-2026-84307/index.md","name":"CVE-2026-84307","record":{"aliases":["GHSA-xwpv-pqxp-5v36"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Filament Laravel components","requires_auth":"none","summary":"An attacker can verify valid passwords for accounts denied panel access by observing MFA challenge responses, leaking credential validity.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-204","name":"Observable Response Discrepancy"}],"description":"Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.12.5 and 5.7.5, packages/panels/src/Auth/Pages/Login.php presents the multi-factor authentication challenge before evaluating canAccessPanel(). For an account that canAccessPanel() denies, submitting the correct password renders the MFA challenge while an incorrect password returns the generic authentication failure, allowing an unauthenticated attacker to confirm whether a candidate password is valid for that account. When email-based MFA is configured, the correct-password path also sends a login code to the account holder. The issue applies only to accounts that have MFA enabled and are denied panel access. Authentication is not bypassed because canAccessPanel() still runs after the challenge, and no session is created. This issue is fixed in versions 4.12.5 and 5.7.5.","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: Password validity disclosure for accounts denied panel access on login page","id":"CVE-2026-84307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"phpseclib — non-constant-time X25519 scalar multiplication permits full private-key recovery","id":"CVE-2026-84308"},"packages":[{"ecosystem":"Packagist","fixed":["4.12.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-xwpv-pqxp-5v36"},{"ecosystem":"Packagist","fixed":["4.12.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-xwpv-pqxp-5v36"},{"ecosystem":"Packagist","fixed":["5.7.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-xwpv-pqxp-5v36"},{"ecosystem":"Packagist","fixed":["5.7.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-xwpv-pqxp-5v36"}],"prev":{"headline":"Filament: Multi-factor authentication (app) codes can still be used after a newer code has been used","id":"CVE-2026-84306"},"products":["filament"],"published":"2026-09-01","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":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["filamentphp"]},"summary":"An attacker can verify valid passwords for accounts denied panel access by observing MFA challenge responses, leaking credential validity.","url":"https://insights.sbomify.com/CVE-2026-84307/"}