What is the CVSS score of CVE-2026-35607?

CVE-2026-35607 has a CVSS 3.1 base score of 8.1 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Filebrowser are affected by CVE-2026-35607?

File Browser versions prior to 2.63.1 contain a privilege escalation vulnerability in proxy authentication that automatically grants command execution permissions to provisioned users, bypassing…. A patch is available.

How to fix or mitigate CVE-2026-35607?

Within 24 hours: Inventory all File Browser deployments and identify those using proxy authentication for user provisioning. Within 7 days: Disable automatic user provisioning via proxy authentication if operationally feasible, or restrict proxy authentication to trusted networks only. Within 30 days: Upgrade to File Browser version 2.63.1 or later once patch availability is confirmed through official vendor channels; validate that security controls are enforced post-upgrade.

Filebrowser CVE-2026-35607

EUVD-2026-19782 HIGH

Improper Privilege Management (CWE-269)

2026-04-07 GitHub_M

GHSA-7526-j432-6ppp

Privilege Escalation Filebrowser

8.1

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.1 HIGH

AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Re-analysis Queued

Apr 16, 2026 - 18:22 vuln.today

cvss_changed

Patch released

Apr 08, 2026 - 02:30 nvd

Patch available

EUVD ID Assigned

Apr 07, 2026 - 17:00 euvd

EUVD-2026-19782

Analysis Generated

Apr 07, 2026 - 17:00 vuln.today

CVE Published

Apr 07, 2026 - 16:31 nvd

HIGH 8.1

DescriptionGitHub Advisory

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.1, the fix in commit b6a4fb1 ("self-registered users don't get execute perms") stripped Execute permission and Commands from users created via the signup handler. The same fix was not applied to the proxy auth handler. Users auto-created on first successful proxy-auth login are granted execution capabilities from global defaults, even though the signup path was explicitly changed to prevent execution rights from being inherited by automatically provisioned accounts. This vulnerability is fixed in 2.63.1.

AnalysisAI

Auto-provisioned users in File Browser's proxy authentication flow inherit elevated execution permissions that were explicitly blocked in the self-registration flow, enabling unauthorized command execution. Versions prior to 2.63.1 grant execute capabilities to proxy-auth users from global defaults, bypassing security controls added in commit b6a4fb1. This affects File Browser instances using proxy authentication for automatic user provisioning. No public exploit identified at time of analysis, though EPSS probability warrants attention given the network-accessible attack surface and high confidentiality/integrity impact.

Technical ContextAI

File Browser is a web-based file management application that supports multiple authentication mechanisms including self-registration and proxy authentication (header-based SSO). The vulnerability stems from inconsistent permission initialization across authentication handlers. While commit b6a4fb1 modified the signup handler to strip Execute permissions and Commands from newly created users, the proxy auth handler continued using unmodified global default permissions. This creates a CWE-269 (Improper Privilege Management) condition where the authentication method determines privilege assignment. In proxy auth scenarios, external authentication systems (reverse proxies, SSO gateways) validate users and pass headers to File Browser, which auto-creates accounts on first login. These auto-created accounts inherit full execution capabilities including shell command execution within the File Browser context, contrary to the intended security posture established for self-registered users.

RemediationAI

Upgrade File Browser to version 2.63.1 or later, which applies consistent permission stripping across both signup and proxy authentication handlers. The fix is implemented in pull request https://github.com/filebrowser/filebrowser/pull/5890, ensuring auto-provisioned proxy-auth users no longer inherit execution capabilities from global defaults. Organizations unable to immediately upgrade should disable proxy authentication and migrate to alternative authentication methods, or implement external controls to prevent untrusted users from reaching the proxy authentication endpoint. Review existing user accounts created via proxy authentication since the deployment of commit b6a4fb1 and manually revoke Execute permissions and Commands through the administrative interface. Consult the GitHub security advisory at https://github.com/filebrowser/filebrowser/security/advisories/GHSA-7526-j432-6ppp for additional vendor guidance.