File Browser share links remain accessible after Share/Download permissions are revoked

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.2 · 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 · score source

EPSS

• CVE-2026-35604: 0.33% estimated exploitation activity in the next 30 days; percentile 26.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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:…

Published by the source

8 Apr 2026, 00:04 UTC

Last modified by the source

8 Apr 2026, 00:04 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-v9w4-gm2x-6rvf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35604

Advisory: File Browser share links remain accessible after Share/Download permissions are revoked
IDs: CVE-2026-35604, GHSA-v9w4-gm2x-6rvf
Record: https://patchnext.com/advisories/cve-2026-35604 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/filebrowser/filebrowser/v2 2.63.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected < 2.63.1; fixed in 2.63.1

## Suggested inspection (read-only)
- Go github.com/filebrowser/filebrowser/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/filebrowser/filebrowser/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-v9w4-gm2x-6rvf (GitHub-reviewed advisory GHSA-v9w4-gm2x-6rvf lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.1)

Commands are suggestions: review each one before running it.