CVE-2026-35607: File Browser Proxy Auth Auto-provisioned Users Inherit Vulnerability

HIGH
Advisory Identifier: GHSA-7526-j432-6ppp
CVSS 8.1
CWE-269
Published
Advisory Summary

CVE-2026-35607 is a HIGH (CVSS 8.1) proxy auth auto-provisioned users inherit vulnerability (CWE-269: Improper Privilege Management) affecting File Browser libraries in the Go ecosystem. The issue involves proxy auth auto-provisioned users inherit execute permission and commands. Remediation is available by upgrading affected packages to version 2.63.1.

CVE-2026-35607 at a Glance

CVE Identifier CVE-2026-35607
GHSA Identifier GHSA-7526-j432-6ppp
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-269: Improper Privilege Management
Affected Product File Browser
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-35607

To remediate this vulnerability, upgrade all affected File Browser 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-35607, inspect your project dependencies for File Browser:

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

Analyze the terminal output to locate any version of File Browser 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-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In File Browser, 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

## Summary 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. Confirmed on v2.62.2 (commit 860c19d). ## Root Cause `auth/proxy.go` `createUser()` applies defaults without restriction: user := &users.User{ Username: username, Password: hashedRandomPassword, LockPassword: true, } setting.Defaults.Apply(user) // No restriction on Execute, Commands, or Admin Compare with `http/auth.go` signup handler (lines 170-178): d.settings.Defaults.Apply(user) user.Perm.Admin = false // Self-registered users should not inherit execution capabilities // from default settings, regardless of what the administrator has // configured as the default. user.Perm.Execute = false user.Commands = []string{} The commit message for `b6a4fb1` states: "Execution rights must be explicitly granted by an admin." Users auto-created via proxy auth are also automatically provisioned (created on first login without explicit admin action), and the admin has not explicitly granted them execution rights. ## PoC Tested on filebrowser v2.62.2, built from HEAD. # Configure with proxy auth, default commands, and exec filebrowser config set --auth.method=proxy --auth.header=X-Remote-User \ --commands "git,ls,cat,id" # Login as admin and verify defaults have execute=true, commands set ADMIN_TOKEN=$(curl -s http://HOST/api/login -H "X-Remote-User: admin") # Auto-create new user via proxy header PROXY_TOKEN=$(curl -s http://HOST/api/login -H "X-Remote-User: newproxyuser") # Check permissions curl -s http://HOST/api/users -H "X-Auth: $ADMIN_TOKEN" | jq '.[] | select(.username=="newproxyuser") | {execute: .perm.execute, commands}' Result: { "execute": true, "commands": ["git", "ls", "cat", "id"] } The auto-created proxy user inherited Execute and the full Commands list. A user created via signup would have `execute: false` and `commands: []`. ## Impact In proxy-auth deployments where the admin has configured default commands, users auto-provisioned on first proxy login receive execution capabilities that were not explicitly granted. The project established a security invariant in commit `b6a4fb1`: automatically provisioned accounts must not inherit execution rights from defaults. The proxy auto-provisioning path violates that invariant. This is an incomplete fix for GHSA-x8jc-jvqm-pm3f ("Signup Grants Execution Permissions When Default Permissions Includes Execution"), which addressed the signup handler but not the proxy auth handler. ## Preconditions - Proxy auth enabled (`--auth.method=proxy`) - Exec not disabled - Default settings include non-empty Commands (admin-configured) ## Suggested Fix Apply the same restrictions as the signup handler: setting.Defaults.Apply(user) user.Perm.Admin = false user.Perm.Execute = false user.Commands = []string{} --- **Update:** Fix submitted as PR #5890.

CVE-2026-35607 Affected File Browser 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-35607?
CVE-2026-35607 is a security vulnerability in File Browser involving Proxy auth auto-provisioned users inherit Execute permission and Commands under CWE-269: Improper Privilege Management.
Which File Browser 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-35607?
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 is the CVSS score of CVE-2026-35607?
CVE-2026-35607 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-35607?
CVE-2026-35607 is classified under CWE-269: Improper Privilege Management (The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.).
How can I check Go dependencies for CVE-2026-35607?
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-7526-j432-6ppp",
  "modified" : "2026-07-21T13:47:07Z",
  "published" : "2026-04-08T00:05:12Z",
  "aliases" : [ "CVE-2026-35607" ],
  "summary" : "File Browser: Proxy auth auto-provisioned users inherit Execute permission and Commands",
  "details" : "## Summary\n\nThe 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.\n\nConfirmed on v2.62.2 (commit 860c19d).\n\n## Root Cause\n\n`auth/proxy.go` `createUser()` applies defaults without restriction:\n\n    user := &users.User{\n        Username:     username,\n        Password:     hashedRandomPassword,\n        LockPassword: true,\n    }\n    setting.Defaults.Apply(user)\n    // No restriction on Execute, Commands, or Admin\n\nCompare with `http/auth.go` signup handler (lines 170-178):\n\n    d.settings.Defaults.Apply(user)\n    user.Perm.Admin = false\n    // Self-registered users should not inherit execution capabilities\n    // from default settings, regardless of what the administrator has\n    // configured as the default.\n    user.Perm.Execute = false\n    user.Commands = []string{}\n\nThe commit message for `b6a4fb1` states: \"Execution rights must be explicitly granted by an admin.\" Users auto-created via proxy auth are also automatically provisioned (created on first login without explicit admin action), and the admin has not explicitly granted them execution rights.\n\n## PoC\n\nTested on filebrowser v2.62.2, built from HEAD.\n\n    # Configure with proxy auth, default commands, and exec\n    filebrowser config set --auth.method=proxy --auth.header=X-Remote-User \\\n      --commands \"git,ls,cat,id\"\n\n    # Login as admin and verify defaults have execute=true, commands set\n    ADMIN_TOKEN=$(curl -s http://HOST/api/login -H \"X-Remote-User: admin\")\n\n    # Auto-create new user via proxy header\n    PROXY_TOKEN=$(curl -s http://HOST/api/login -H \"X-Remote-User: newproxyuser\")\n\n    # Check permissions\n    curl -s http://HOST/api/users -H \"X-Auth: $ADMIN_TOKEN\" | jq '.[] | select(.username==\"newproxyuser\") | {execute: .perm.execute, commands}'\n\nResult:\n\n    {\n      \"execute\": true,\n      \"commands\": [\"git\", \"ls\", \"cat\", \"id\"]\n    }\n\nThe auto-created proxy user inherited Execute and the full Commands list. A user created via signup would have `execute: false` and `commands: []`.\n\n## Impact\n\nIn proxy-auth deployments where the admin has configured default commands, users auto-provisioned on first proxy login receive execution capabilities that were not explicitly granted. The project established a security invariant in commit `b6a4fb1`: automatically provisioned accounts must not inherit execution rights from defaults. The proxy auto-provisioning path violates that invariant.\n\nThis is an incomplete fix for GHSA-x8jc-jvqm-pm3f (\"Signup Grants Execution Permissions When Default Permissions Includes Execution\"), which addressed the signup handler but not the proxy auth handler.\n\n## Preconditions\n\n- Proxy auth enabled (`--auth.method=proxy`)\n- Exec not disabled\n- Default settings include non-empty Commands (admin-configured)\n\n## Suggested Fix\n\nApply the same restrictions as the signup handler:\n\n    setting.Defaults.Apply(user)\n    user.Perm.Admin = false\n    user.Perm.Execute = false\n    user.Commands = []string{}\n\n---\n\n**Update:** Fix submitted as PR #5890.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "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-7526-j432-6ppp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35607"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/filebrowser/filebrowser/pull/5890"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/filebrowser/filebrowser"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-269" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-08T00:05:12Z",
    "nvd_published_at" : "2026-04-07T17:16:34Z"
  }
}