Account access persistence via replayable logout JWTs
Published Jul 15, 2025 · Updated Jul 15, 2025
Insufficient session expiration in File Browser 2.39.0 allows remote attackers with a captured JWT to retain authenticated access after logout. The backend maintains no active-session registry or token blacklist, so auth.go continues to accept a logged-out JWT until its natural expiration. Possession of a previously issued token is required; replay grants the token holder the same authenticated API access and file permissions as the original session.
Summary
What happened
Insufficient session expiration in File Browser 2.39.0 allows remote attackers with a captured JWT to retain authenticated access after logout. The backend maintains no active-session registry or token blacklist, so auth.go continues to accept a logged-out JWT until its natural expiration. Possession of a previously issued token is required; replay grants the token holder the same authenticated API access and file permissions as the original session.
The record
- CVE
- CVE-2025-53826
- Published
- Jul 15, 2025
- Updated
- Jul 15, 2025
- Vendor
- File Browser
- Product
- File Browser
- Classifications
- CWE-385, CWE-305, CWE-613, T1550.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2025CVE publishedPublication date reported by the CVE source.
- Jul 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 2.39.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA post-logout JWT replay proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo