CVE-2026-73611

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

File Browser versions from 2.50.0 through 2.63.21 fail to validate JWT expiration when proxy authentication is configured with a non-default logout page. Attackers with a previously valid token can access protected routes and administrative endpoints indefinitely, and exchange expired tokens for fresh ones via the renewal endpoint.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
47(Track*)
EG Risk 47/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity68% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 14, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

File Browser 2.50.0 through 2.63.21 JWT Expiration Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/file-browser-through-jwt-expiration-bypass
github_commit

commit 72faf6dd3c85 (filebrowser/filebrowser)

Fix landed in filebrowser/filebrowser commit 72faf6dd3c85 — awaiting tagged release

https://github.com/filebrowser/filebrowser/commit/72faf6dd3c85628e332d3e567124b86708ce2695
github Patch Available🟡 PoC Available

Expired JWTs accepted under proxy auth with a custom logout page · Advisory · filebrowser/filebrowser · GitHub

Affected: v2.63.22. The expiration is now waived only when the configured proxy header stil

https://github.com/filebrowser/filebrowser/security/advisories/GHSA-v3jv-rmh2-635j

Vendor Advisories for CVE-2026-73611(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 11:55 UTCEG score recompute
  3. 2026-08-20 11:55 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 13:47 UTCGHSA enrichment
  6. 2026-08-18 15:42 UTCEG score recompute
  7. 2026-08-18 15:42 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-17 17:37 UTCEG score recompute
  11. 2026-08-17 17:36 UTCGHSA enrichment
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 19:30 UTCEG score recompute
  14. 2026-08-16 19:30 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 02:15 UTCEPSS rescore
  18. 2026-08-15 21:25 UTCEG score recompute
  19. 2026-08-15 21:25 UTCGHSA enrichment
  20. 2026-08-15 01:31 UTCEPSS rescore
  21. 2026-08-14 23:19 UTCEG score recompute
  22. 2026-08-14 23:19 UTCGHSA enrichment
  23. 2026-08-14 22:39 UTCEG score recompute
  24. 2026-08-14 22:39 UTCGHSA enrichment
  25. 2026-08-14 17:08 UTCEG score recompute
Show 6 more
  1. 2026-08-14 17:08 UTCGHSA enrichment
  2. 2026-08-14 10:38 UTCGHSA enrichment
  3. 2026-08-13 12:33 UTCEG score recompute
  4. 2026-08-13 12:33 UTCGHSA enrichment
  5. 2026-08-13 11:42 UTCEG score recompute
  6. 2026-08-13 11:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73611?
CVE-2026-73611 is a medium vulnerability published on August 13, 2026. File Browser versions from 2.50.0 through 2.63.21 fail to validate JWT expiration when proxy authentication is configured with a non-default logout page. Attackers with a previously valid token can access protected routes and administrative endpoints indefinitely, and exchange expired tokens for…
When was CVE-2026-73611 disclosed?
CVE-2026-73611 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73611 actively exploited?
CVE-2026-73611 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-73611?
CVE-2026-73611 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-73611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73611, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-73611

Explore →

Is Your Infrastructure Affected by CVE-2026-73611?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs