CVE-2026-73611
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.34%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 4.0
- 7.6 HIGHCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M
- EPSS
- 0.34% probability · 27th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-613
- Source
- disclosure@vulncheck.com
References
- https://github.com/filebrowser/filebrowser/commit/72faf6dd3c85628e332d3e567124b86708ce2695
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-v3jv-rmh2-635j
- https://www.vulncheck.com/advisories/file-browser-through-jwt-expiration-bypass
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-v3jv-rmh2-635j
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.