{"answers":{"affected":"4 open source packages ship an affected version, including filament/filament.","exploited":"There is no known exploitation of CVE-2026-48166 in the wild and no public exploit code.","fix":"Upgrade filament/filament to a fixed version for your release line: 4.11.5 or 5.6.5.","what":"CVE-2026-48166 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 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-48166 and fix it if it is affected.\n\nWhat it is: CVE-2026-48166 is a medium-severity vulnerability in filamentphp filament, published on 22 Jun 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-48166 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.11.5\n- filament/filament (Packagist): affected from 4.0.0; fixed in 4.11.5\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.5\n- filament/filament (Packagist): affected from 5.0.0; fixed in 5.6.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-48166/ (Markdown: https://insights.sbomify.com/CVE-2026-48166/index.md)","id":"CVE-2026-48166","markdown":"https://insights.sbomify.com/CVE-2026-48166/index.md","name":"CVE-2026-48166","record":{"aliases":["GHSA-5w46-g9pq-wh6f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Laravel development framework","requires_auth":"none","summary":"Unauthenticated attackers can enumerate registered email addresses via timing discrepancies on the login page of Filament applications.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"Filament is a collection of full-stack components for accelerated Laravel development. From 4.0.0 until 4.11.5 and 5.6.5, the login page has an observable timing discrepancy that allows unauthenticated attackers to enumerate registered email addresses. The impact is limited to disclosing whether an account exists for a given email. This vulnerability is fixed in 4.11.5 and 5.6.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: Timing-based user enumeration on login page","id":"CVE-2026-48166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Filament: Unvalidated ImageColumn and ImageEntry values can be used for XSS","id":"CVE-2026-48167"},"packages":[{"ecosystem":"Packagist","fixed":["4.11.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-5w46-g9pq-wh6f"},{"ecosystem":"Packagist","fixed":["4.11.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-5w46-g9pq-wh6f"},{"ecosystem":"Packagist","fixed":["5.6.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-5w46-g9pq-wh6f"},{"ecosystem":"Packagist","fixed":["5.6.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-5w46-g9pq-wh6f"}],"prev":{"headline":"MariaDB: unsafe usage of `wsrep_sst_receive_address` values on the joiner side","id":"CVE-2026-48165"},"products":["filament"],"published":"2026-06-22","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["filamentphp"]},"summary":"Unauthenticated attackers can enumerate registered email addresses via timing discrepancies on the login page of Filament applications.","url":"https://insights.sbomify.com/CVE-2026-48166/"}