{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73611 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-73611 is a high-severity authentication bypass vulnerability in filebrowser, published on 13 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-73611 and fix it if it is affected.\n\nWhat it is: CVE-2026-73611 is a high-severity authentication bypass vulnerability in filebrowser, published on 13 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-73611 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-73611/ (Markdown: https://insights.sbomify.com/CVE-2026-73611/index.md)","id":"CVE-2026-73611","markdown":"https://insights.sbomify.com/CVE-2026-73611/index.md","name":"CVE-2026-73611","record":{"aliases":["GHSA-32pr-94pq-34pj","GHSA-v3jv-rmh2-635j","MINI-9xmf-f58f-8gvq","MINI-ppmh-cr3x-473g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"File Browser","requires_auth":"low_privilege","summary":"Attackers can bypass JWT expiration checks in File Browser when proxy authentication is configured, allowing indefinite access to protected and administrative routes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"File Browser versions from 2.50.0 through 2.63.21 fail to validate JWT expiration when proxy authentication is configured with a non-default logout page. Attackers with a previously valid token can access protected routes and administrative endpoints indefinitely, and exchange expired tokens for fresh ones via the renewal endpoint.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"File Browser 2.50.0 through 2.63.21 JWT Expiration Bypass","id":"CVE-2026-73611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"File Browser before v2.63.22 Authorization Bypass via Recursive Operations","id":"CVE-2026-73612"},"packages":[],"prev":{"headline":"SiYuan before v3.7.4 Information Disclosure via Local Storage","id":"CVE-2026-73610"},"products":["filebrowser"],"published":"2026-08-13","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":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["filebrowser"]},"summary":"Attackers can bypass JWT expiration checks in File Browser when proxy authentication is configured, allowing indefinite access to protected and administrative routes.","url":"https://insights.sbomify.com/CVE-2026-73611/"}