CVE-2026-28492

When a user creates a public share link for a directory, the withHashFile middleware in http/public.go (line 59) uses filepath.Dir(link.Path) to compute the BasePathFs root. This sets the filesystem root to the parent directory instead of the shared directory itself, allowing anyone with the share link to browse and download files from all sibling directories.

Details

In http/public.go lines 52-64, the withHashFile function handles public share link requests:

basePath := link.Path    // e.g. "/documents/shared"
filePath := ""

if file.IsDir {
    basePath = filepath.Dir(basePath)  // BUG: becomes "/documents" (parent!)
    filePath = ifPath
}

d.user.Fs = afero.NewBasePathFs(d.user.Fs, basePath)

When a directory at /documents/shared is shared, filepath.Dir("/documents/shared") evaluates to "/documents". The BasePathFs is then rooted at the parent directory /documents/, giving the share link access to everything under /documents/ - not just the intended /documents/shared/.

This affects both publicShareHandler (directory listing via /api/public/share/{hash}) and publicDlHandler (file download via /api/public/dl/{hash}/path).

PoC

1. Set up filebrowser with a user whose scope contains:
2. • /documents/shared/public-file.txt (intended to be shared)
3. • /documents/secrets/passwords.txt (NOT intended to be shared)
4. • /documents/private/financial.csv (NOT intended to be shared)
5. Create a public share link for the directory /documents/shared (via POST /api/share/documents/shared)
6. Access the share link: GET /api/public/share/{hash}
7. • Expected: Lists only contents of /documents/shared/
8. • Actual: Lists contents of /documents/ (parent), revealing secrets/, private/, and shared/ directories
9. Download sibling files: GET /api/public/dl/{hash}/secrets/passwords.txt
10. • Expected: 404 or 403 (file outside share scope)
11. • Actual: 200 with file contents (sibling file downloaded successfully)

Standalone Go test reproducing the exact vulnerable code path with afero.NewBasePathFs:

func TestShareScopeEscape(t *testing.T) {
    baseFs := afero.NewMemMapFs()
    afero.WriteFile(baseFs, "/documents/shared/public.txt", []byte("public"), 0644)
    afero.WriteFile(baseFs, "/documents/secrets/passwords.txt", []byte("admin:hunter2"), 0644)

    linkPath := "/documents/shared"
    basePath := filepath.Dir(linkPath) // BUG: "/documents"
    scopedFs := afero.NewBasePathFs(baseFs, basePath)

    // Sibling file is accessible through the share:
    f, err := scopedFs.Open("/secrets/passwords.txt")
    // err is nil - file accessible! Content: "admin:hunter2"
}

This test passes, confirming the vulnerability.

Unauthenticated information disclosure (CWE-200, CWE-706). Anyone with a public share link for a directory can:

• Browse all sibling directories and files of the shared directory
• • Download any file within the parent directory scope
• • This works without authentication (public shares) or after providing the share password (password-protected shares)
    All filebrowser v2.x installations that use directory sharing are affected.

Kodem intelligence

Remove the filepath.Dir() call and use link.Path directly as the BasePathFs root:

if file.IsDir {
    // Don't change basePath - keep it as link.Path
    filePath = ifPath
}
d.user.Fs = afero.NewBasePathFs(d.user.Fs, basePath)

Affected commit: e3d00d591b567a8bfe3b02e42ba586859002c77d (latest)
File: http/public.go, line 59

1. What is CVE-2026-28492? CVE-2026-28492 is a high-severity security vulnerability in github.com/filebrowser/filebrowser/v2 (go), affecting versions <= 2.60.0. It is fixed in 2.61.0.
2. Which versions of github.com/filebrowser/filebrowser/v2 are affected by CVE-2026-28492? github.com/filebrowser/filebrowser/v2 (go) versions <= 2.60.0 is affected.
3. Is there a fix for CVE-2026-28492? Yes. CVE-2026-28492 is fixed in 2.61.0. Upgrade to this version or later.
4. Is CVE-2026-28492 exploitable, and should I be worried? Whether CVE-2026-28492 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-28492 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-28492? Upgrade github.com/filebrowser/filebrowser/v2 to 2.61.0 or later.