Quick answers
- Is CVE-2026-116682 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116682 being exploited in the wild.
- How severe is CVE-2026-116682?
- High severity, with a CVSS score of 8.6, published 27 October 2026.
- Which products and versions are affected?
- github.com/gtsteffaniak/filebrowser/backend (Go) < 0.0.0-20260814233832-4126edeb07a0, SEMVER:introduced=0,fixed=0.0.0-20260814233832-4126edeb07a0; Gtsteffaniak FileBrowser before 1.5.2-stable and before 2.0.1-beta.
- Is there a fix for CVE-2026-116682?
- Yes. github.com/gtsteffaniak/filebrowser/backend (Go): upgrade to 0.0.0-20260814233832-4126edeb07a0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116682 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116682?
- Check whether you run github.com/gtsteffaniak/filebrowser/backend (Go) or Gtsteffaniak FileBrowser 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/gtsteffaniak/filebrowser/backend (Go): upgrade to 0.0.0-20260814233832-4126edeb07a0 or later
go get github.com/gtsteffaniak/filebrowser/backend@v0.0.0-20260814233832-4126edeb07a0
Technical details
The vulnerability exists in backend/pkg/indexing/indexingFiles.go where GetRealPath resolves symbolic links without validating that the resolved target remains within the source root and user's authorized scope. Multiple read flows (download, preview, media, OnlyOffice, public-share) that enable FollowSymlinks are affected. An authenticated user with download access or a public-share holder can exploit reachable in-scope symlinks to access out-of-scope files.
Affected products
- gtsteffaniak FileBrowser before 1.5.2-stable and before 2.0.1-beta
Identifiers
- CVE-2026-116682
- GHSA-mgqf-5mf5-prfj
- GO-2026-6870
Timeline
- 2026-10-27: disclosed