{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82237 exists.","fix":"No fix has been published for CVE-2026-82237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82237 is a low-severity vulnerability in filebrowser, published on 28 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-82237 and fix it if it is affected.\n\nWhat it is: CVE-2026-82237 is a low-severity vulnerability in filebrowser, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82237 exists.\n\nAffected product: filebrowser. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-82237/ (Markdown: https://insights.sbomify.com/CVE-2026-82237/index.md)","id":"CVE-2026-82237","markdown":"https://insights.sbomify.com/CVE-2026-82237/index.md","name":"CVE-2026-82237","record":{"aliases":["GHSA-m8v4-4w34-rrvf","GHSA-v6g4-hccq-frhr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"filebrowser web app","requires_auth":"low_privilege","summary":"Attackers can access unrelated files via stale share links if files are renamed, exposing data unexpectedly in filebrowser.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"}],"description":"filebrowser through 2.63.23 does not remove share records when a shared file is renamed (only deletion triggers share cleanup). The share record is keyed by path, so it survives the rename and remains dormant (returning 404 while the path is empty). When any new, unrelated file later appears at the original shared path — via re-upload, another user with create permission, or a hook — the stale public share link serves that new file under the original link's password and expiry settings, unexpectedly exposing it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"filebrowser through 2.63.23 Stale Share Link via File Rename","id":"CVE-2026-82237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"filebrowser 2.24.0 Race Condition via TUS concurrent PATCH uploads","id":"CVE-2026-82238"},"packages":[],"prev":{"headline":"File Browser 2.63.6 through 2.63.23 Share Link Exposure via File Deletion","id":"CVE-2026-82236"},"products":["filebrowser"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-28","vendors":["filebrowser"]},"summary":"Attackers can access unrelated files via stale share links if files are renamed, exposing data unexpectedly in filebrowser.","url":"https://insights.sbomify.com/CVE-2026-82237/"}