{"answers":{"affected":"4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser.","exploited":"There is no known exploitation of CVE-2026-62684 in the wild and no public exploit code.","fix":"Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.17 or later.","what":"CVE-2026-62684 is a low-severity vulnerability in filebrowser, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62684 and fix it if it is affected.\n\nWhat it is: CVE-2026-62684 is a low-severity vulnerability in filebrowser, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62684 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17\n- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17\n- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17\n- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed\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-62684/ (Markdown: https://insights.sbomify.com/CVE-2026-62684/index.md)","id":"CVE-2026-62684","markdown":"https://insights.sbomify.com/CVE-2026-62684/index.md","name":"CVE-2026-62684","record":{"aliases":["GHSA-833g-cqhp-h72j","GO-2026-6025"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"File Browser","requires_auth":"high_privilege","summary":"File Browser exposes password hashes and bypass tokens via API responses, allowing attackers to crack passwords or access protected shares.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.17, the Link storage struct is serialized directly by sharePostHandler, shareListHandler, and shareGetsHandler through renderJSON, causing POST /api/share/{path} and GET /api/shares to expose password_hash and the bypass token, while an administrator can retrieve these secrets for every user's shares, enabling offline password cracking and direct access to protected shares. This issue is fixed in version 2.63.17.","ecosystems":["Go"],"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":"File Browser: Share API exposes the password hash and bypass token","id":"CVE-2026-62684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"File Browser: Colliding username normalization gives two users the same home directory","id":"CVE-2026-62685"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/filebrowser/filebrowser","purl":"pkg:golang/github.com/filebrowser/filebrowser","source":"GO-2026-6025"},{"ecosystem":"Go","fixed":["2.63.17"],"introduced":["0"],"last_affected":[],"package":"github.com/filebrowser/filebrowser/v2","purl":null,"source":"GHSA-833g-cqhp-h72j"},{"ecosystem":"Go","fixed":["2.63.17"],"introduced":["0"],"last_affected":[],"package":"github.com/filebrowser/filebrowser/v2","purl":"pkg:golang/github.com/filebrowser/filebrowser/v2","source":"GHSA-833g-cqhp-h72j"},{"ecosystem":"Go","fixed":["2.63.17"],"introduced":["0"],"last_affected":[],"package":"github.com/filebrowser/filebrowser/v2","purl":"pkg:golang/github.com/filebrowser/filebrowser/v2","source":"GO-2026-6025"}],"prev":{"headline":"File Browser: Trailing-slash delete leaves a stale public share behind","id":"CVE-2026-62683"},"products":["filebrowser"],"published":"2026-08-18","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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-08-18","vendors":["filebrowser"]},"summary":"File Browser exposes password hashes and bypass tokens via API responses, allowing attackers to crack passwords or access protected shares.","url":"https://insights.sbomify.com/CVE-2026-62684/"}