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

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

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** CVE-2026-54095, GHSA-7xwp-2cpp-p8r7, GO-2025-3812

## 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 (DEPRECATED: Insufficient Session Expiration), CWE-385 (Covert Timing Channel), CWE-305 (Authentication Bypass by Primary Weakness)

## 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.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 2.39.0 | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 2.39.0 | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions to 2.39.0 | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions to 2.39.0 | None |

Products: 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.

## Other vulnerabilities in filebrowser

- [CVE-2026-32760](https://insights.sbomify.com/CVE-2026-32760/): File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin (critical 10.0)
- [CVE-2026-29188](https://insights.sbomify.com/CVE-2026-29188/): File Browser: TUS Delete Endpoint Bypasses Delete Permission Check (critical 9.1)
- [CVE-2023-39612](https://insights.sbomify.com/CVE-2023-39612/): Cross-site scripting in n/a (critical 9.0)
- [CVE-2026-30934](https://insights.sbomify.com/CVE-2026-30934/): FileBrowser Quantum: Stored XSS in public share page via unsanitized share metadata (text/template misuse) (high 8.9)
- [CVE-2021-46398](https://insights.sbomify.com/CVE-2021-46398/): Cross-Site Request Forgery in Filebrowser (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53826 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53826 exists.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 2.39.0; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 2.39.0; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions up to 2.39.0; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions up to 2.39.0; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53826/ (Markdown: https://insights.sbomify.com/CVE-2025-53826/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53826
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53826
- OSV: https://osv.dev/vulnerability/CVE-2025-53826

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53826/
Summaries are generated and may contain mistakes; the official description above is the record.