Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

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

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

CVSS 7.7 HighEPSS 0.0055 · 46th percentile

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.

PackageEcosystemAffectedFixed in
github.com/filebrowser/filebrowserGo<=2.39.0No fixed version yet
github.com/filebrowser/filebrowser/v2Go<=2.39.0No fixed version yet
Identifiers
GHSA-7xwp-2cpp-p8r7 · CVE-2025-53826 · GO-2025-3812
Weakness (CWE)
CWE-305 · CWE-384 · CWE-385 · CWE-613
Tags
Published
16 Jul 2025
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
7.7 High 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 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

  1. 31 Oct 2026, 14:14 UTC First seen by agentprime
  2. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

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.