# CVE-2026-62684: File Browser: Share API exposes the password hash and bypass token

> File Browser exposes password hashes and bypass tokens via API responses, allowing attackers to crack passwords or access protected shares.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-833g-cqhp-h72j, GO-2026-6025

## What is CVE-2026-62684?

CVE-2026-62684 is a low-severity vulnerability in filebrowser, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.17, the Link storage struct is serialized directly by sharePostHandler, shareListHandler, and shareGetsHandler through renderJSON, causing POST /api/share/{path} and GET /api/shares to expose password_hash and the bypass token, while an administrator can retrieve these secrets for every user's shares, enabling offline password cracking and direct access to protected shares. This issue is fixed in version 2.63.17.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-62684?

4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.17 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.17 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.17 |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |

## How do I fix CVE-2026-62684?

Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.17 or later.

## Is CVE-2026-62684 being exploited?

There is no known exploitation of CVE-2026-62684 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62684 and fix it if it is affected.

What it is: CVE-2026-62684 is a low-severity vulnerability in filebrowser, published on 18 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62684 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.17
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62684/ (Markdown: https://insights.sbomify.com/CVE-2026-62684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62684
- OSV: https://osv.dev/vulnerability/CVE-2026-62684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62684/
Summaries are generated and may contain mistakes; the official description above is the record.