# File Browser’s insecure JWT handling can lead to session replay attacks after logout

Advisory record · `GHSA-7xwp-2cpp-p8r7`

- **Identifiers:** `GHSA-7xwp-2cpp-p8r7` · `CVE-2025-53826` · `GO-2025-3812`
- **State:** Confirmed
- **Severity:** CVSS 7.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-305](https://cwe.mitre.org/data/definitions/305.html) · [CWE-384](https://cwe.mitre.org/data/definitions/384.html) · [CWE-385](https://cwe.mitre.org/data/definitions/385.html) · [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md) · [CWE-305](https://agentprime.io/advisories/tag/cwe-305.md) · [CWE-385](https://agentprime.io/advisories/tag/cwe-385.md)
- **Published:** 16 Jul 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 Jul 2025, 14:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/filebrowser/filebrowser` (Go): affected `<=2.39.0`; no fixed version yet
- `github.com/filebrowser/filebrowser/v2` (Go): affected `<=2.39.0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> File Browser versions up to and including 2.39.0 (Go modules github.com/filebrowser/filebrowser and github.com/filebrowser/filebrowser/v2) issue JWT tokens that remain valid after the user logs out, because logout does not invalidate them on the server. An attacker who has captured a token can replay it to access authenticated endpoints until it expires. No fix is listed; the source suggests reducing token lifetime as a mitigation.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.7 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0055, the 46th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:14 UTC: First seen by agentprime
- 31 Oct 2026, 14:14 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-7xwp-2cpp-p8r7)

## Sources

- [GitHub Advisory Database: GHSA-7xwp-2cpp-p8r7](https://github.com/advisories/GHSA-7xwp-2cpp-p8r7)
- [OSV: GHSA-7xwp-2cpp-p8r7](https://osv.dev/vulnerability/GHSA-7xwp-2cpp-p8r7)
- <https://github.com/filebrowser/filebrowser/security/advisories/GHSA-7xwp-2cpp-p8r7>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-53826>
- <https://github.com/filebrowser/filebrowser/issues/5216>
- <https://github.com/filebrowser/filebrowser>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-7xwp-2cpp-p8r7>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7xwp-2cpp-p8r7/>. Everything for agents: <https://agentprime.io/llms.txt>.