Is CVE-2026-62684 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-62684 being exploited in the wild.

How severe is CVE-2026-62684?

Low severity, with a CVSS score of 3.1, published 20 July 2026.

Which products and versions are affected?

File Browser <= 2.63.16; github.com/filebrowser/filebrowser (Go) SEMVER:introduced=0; github.com/filebrowser/filebrowser/v2 (Go) <= 2.63.16, SEMVER:introduced=0,fixed=2.63.17.

Is there a fix for CVE-2026-62684?

Yes. github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-62684 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-62684?

Check whether you run File Browser, github.com/filebrowser/filebrowser (Go) or github.com/filebrowser/filebrowser/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62684: File Browser sensitive information disclosure in Share API

Q: Which products and versions are affected?

File Browser <= 2.63.16; github.com/filebrowser/filebrowser (Go) SEMVER:introduced=0; github.com/filebrowser/filebrowser/v2 (Go) <= 2.63.16, SEMVER:introduced=0,fixed=2.63.17.

Q: Is there a fix for CVE-2026-62684?

Yes. github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-62684 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-62684?

Check whether you run File Browser, github.com/filebrowser/filebrowser (Go) or github.com/filebrowser/filebrowser/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-62684 · Severity: low · CVSS 3.1 · Published 2026-07-20

File Browser, a web-based file management utility, contains a security flaw where the system inadvertently shares sensitive security credentials through its programming interface. When a user or administrator views shared files, the system includes the encrypted password hashes and secret access tokens in the data sent to the browser. This allows an attacker to potentially crack passwords offline or bypass security controls to access protected files without authorization.

Technologies: File Browser, github.com/filebrowser/filebrowser (Go), github.com/filebrowser/filebrowser/v2 (Go). Vendors: File Browser, Go.

Quick answers

Is CVE-2026-62684 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-62684 being exploited in the wild.
How severe is CVE-2026-62684?: Low severity, with a CVSS score of 3.1, published 20 July 2026.
Which products and versions are affected?: File Browser <= 2.63.16; github.com/filebrowser/filebrowser (Go) SEMVER:introduced=0; github.com/filebrowser/filebrowser/v2 (Go) <= 2.63.16, SEMVER:introduced=0,fixed=2.63.17.
Is there a fix for CVE-2026-62684?: Yes. github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-62684 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-62684?: Check whether you run File Browser, github.com/filebrowser/filebrowser (Go) or github.com/filebrowser/filebrowser/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.17 or later
```
go get github.com/filebrowser/filebrowser/v2@v2.63.17
```

Technical details

A sensitive information disclosure vulnerability exists in File Browser due to improper serialization of the 'Link' storage struct. The API handlers for creating and listing shares (POST /api/share and GET /api/shares) use unfiltered json.Marshal on the internal struct, which includes 'password_hash' and 'token' fields. An authenticated user can retrieve these secrets for their own shares, while an administrator can retrieve them for all users' shares. This enables offline brute-force attacks against bcrypt hashes and immediate unauthorized access to protected shares using the leaked bypass tokens. The issue is fixed in version 2.63.17 by removing these fields from the JSON output.

Affected products

filebrowser filebrowser <= 2.63.16

Identifiers

CVE-2026-62684
GHSA-833g-cqhp-h72j
GO-2026-6025

Timeline

2026-07-04: disclosed
2026-07-20: advisory
2026-07-20: patched: Fixed in version 2.63.17

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.