Skip to main content
VulnerabilityPublished Updated

CVE-2026-73611: filebrowser · Insufficient Session Expiration

Affects filebrowserSource CVE Database V5

0
Compare

Public exploit available · CVSS 7.6 High : upgrade to 2.63.22 as a priority.

Data as of 20 Nov 2026, 13:04 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.6
CNA (VulnCheck)CVSS 3.16.8
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-08-14.

Patch
Available – fixed in 2.63.22
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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by VulnCheck

    , 12 minutes before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 35 hours after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade filebrowser to 2.63.22.

Affected software

ProductAffectedFixed in
filebrowserfilebrowserAffected
  • >=2.50.0 <2.63.22
Fixed in
  • 2.63.22
Gofilebrowserpkg:golang/filebrowserOther threatsAffected
  • >=2.50.0 <2.63.22
Fixed in
  • 2.63.22

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade File Browser to version 2.63.22 or later, where this vulnerability is fixed. No other mitigations are indicated in the vendor advisory or data provided.

Description

File Browser versions from 2.50.0 up to but not including 2.63.22 contain a vulnerability where JWT expiration is not properly validated when proxy authentication is configured with a non-default logout page. This flaw allows attackers possessing previously valid tokens to maintain indefinite access to protected and administrative routes, and to renew expired tokens via a renewal endpoint. The issue is fixed in version 2.63.22.

References

Community reviews

Loading reviews…