CVE-2025-53826 FileBrowser Has Insecure JWT Handling Which Allows Session Replay Attacks after Logout

High 7.7 Published Updated

Attackers can replay stolen JWT tokens to maintain access after logout, bypassing session termination in File Browser.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-53826?

CVE-2025-53826 is a high-severity vulnerability in filebrowser, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename, and edit files. In version 2.39.0, File Browser’s authentication system issues long-lived JWT tokens that remain valid even after the user logs out. As of time of publication, no known patches exist.

Weakness: CWE-613, CWE-385, CWE-305

Which versions are affected by CVE-2025-53826?

6 open source packages ship an affected version, including github.com/filebrowser/filebrowser and github.com/filebrowser/filebrowser/v2. It affects 1 product.

PackageAffectedFixed in
github.com/filebrowser/filebrowser GoAll versionsNone
github.com/filebrowser/filebrowser GoAll versions to 2.39.0None
github.com/filebrowser/filebrowser GoAll versions to 2.39.0None
github.com/filebrowser/filebrowser/v2 GoAll versionsNone
github.com/filebrowser/filebrowser/v2 GoAll versions to 2.39.0None
github.com/filebrowser/filebrowser/v2 GoAll versions to 2.39.0None

Products include Filebrowser Filebrowser.

How do I fix CVE-2025-53826?

No fix published yet.

Is CVE-2025-53826 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53826 exists.

Sources

Also known as CVE-2026-54095, GHSA-7xwp-2cpp-p8r7, GO-2025-3812.

Is CVE-2025-53826 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free