File Browser discloses text file content via /api/resources endpoint bypassing Perm.Download check

Exploitation

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

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-35606: 0.34% estimated exploitation activity in the next 30 days; percentile 27.41 (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.

Summary The resourceGetHandler in http/resource.go returns full text file content without checking the Perm.Download permission flag. All three other content-serving endpoints (/api/raw, /api/preview, /api/subtitle) correctly verify this permission before serving content. A user with download: false can read any text file within their scope through two bypass paths. Confirmed on v2.62.2 (commit 860c19d). Root Cause http/resource.go line 26-33 hardcodes Content: true in the FileOptions without checking download permission: file, err := files.NewFileInfo(&files.FileOptions{ ... Content: true, // Always loads text content, no permission check }) Lines 44-63: the X-Encoding: true header path reads the entire file and returns raw bytes as application/octet-stream, also without any download check. Compare with the three protected endpoints: // raw.go:83-85 if !d.user.Perm.Download { return http.StatusAccepted, nil } // preview.go:38-40 if !d.user.Perm.Download { return http.StatusAccepted,…

Published by the source

8 Apr 2026, 00:05 UTC

Last modified by the source

8 Apr 2026, 00:05 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-67cg-cpj7-qgc9

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

# Patch Next advisory brief: CVE-2026-35606

Advisory: File Browser discloses text file content via /api/resources endpoint bypassing Perm.Download check
IDs: CVE-2026-35606, GHSA-67cg-cpj7-qgc9
Record: https://patchnext.com/advisories/cve-2026-35606 (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: Medium (CVSS 5.3)
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-67cg-cpj7-qgc9 (GitHub-reviewed advisory GHSA-67cg-cpj7-qgc9 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.63.1)

Commands are suggestions: review each one before running it.