{"answers":{"affected":"4 open source packages ship an affected version, including filament/filament.","exploited":"There is no known exploitation of CVE-2026-48505 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-48505 is a high-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-48505 and fix it if it is affected.\n\nWhat it is: CVE-2026-48505 is a high-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-48505 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-48505/ (Markdown: https://insights.sbomify.com/CVE-2026-48505/index.md)","id":"CVE-2026-48505","markdown":"https://insights.sbomify.com/CVE-2026-48505/index.md","name":"CVE-2026-48505","record":{"aliases":["GHSA-mc5j-f6wx-h9qh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Filament Laravel framework","requires_auth":"none","summary":"Attackers can reuse MFA recovery codes via concurrent requests, gaining multiple authenticated sessions if they possess user credentials and recovery codes.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-841","name":"Improper Enforcement of Behavioral Workflow"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"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, a flaw in the handling of recovery codes for app-based multi-factor authentication allows the same recovery code to be reused via concurrent submission. This issue does not affect email-based MFA. It also only applies when recovery codes are enabled. If an attacker gains access to both the user's password and their recovery codes, they get two authenticated sessions per recovery code burned instead of one, or more if they batch the parallel submissions wider, materially extending the attacker's window of access compared to what the single-use guarantee implies. 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: Multi-factor authentication (app) recovery codes can still be used multiple times via concurrent submission","id":"CVE-2026-48505","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"MessagePack-CSharp: MessagePackReader.Skip can recurse without enforcing maximum object graph depth","id":"CVE-2026-48506"},"packages":[{"ecosystem":"Packagist","fixed":["4.11.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-mc5j-f6wx-h9qh"},{"ecosystem":"Packagist","fixed":["4.11.5"],"introduced":["4.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-mc5j-f6wx-h9qh"},{"ecosystem":"Packagist","fixed":["5.6.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":null,"source":"GHSA-mc5j-f6wx-h9qh"},{"ecosystem":"Packagist","fixed":["5.6.5"],"introduced":["5.0.0"],"last_affected":[],"package":"filament/filament","purl":"pkg:composer/filament/filament","source":"GHSA-mc5j-f6wx-h9qh"}],"prev":{"headline":"OpenTelemetry Rust: Unbounded memory allocation in W3C Baggage propagation","id":"CVE-2026-48504"},"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["filamentphp"]},"summary":"Attackers can reuse MFA recovery codes via concurrent requests, gaining multiple authenticated sessions if they possess user credentials and recovery codes.","url":"https://insights.sbomify.com/CVE-2026-48505/"}