Command execution via inherited proxy-user defaults
Published Apr 7, 2026 · Updated Apr 7, 2026
Improper privilege management in File Browser before 2.63.1 allows remote attackers to gain configured command-execution rights through proxy login. The auth/proxy.go createUser function applies global defaults without clearing Execute permission or the Commands list for accounts created on first login. Exposure requires proxy authentication, enabled execution, and nonempty default commands; an auto-provisioned account can then run those configured commands.
Summary
What happened
Improper privilege management in File Browser before 2.63.1 allows remote attackers to gain configured command-execution rights through proxy login. The auth/proxy.go createUser function applies global defaults without clearing Execute permission or the Commands list for accounts created on first login. Exposure requires proxy authentication, enabled execution, and nonempty default commands; an auto-provisioned account can then run those configured commands.
The record
- CVE
- CVE-2026-35607
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- File Browser Contributors
- Product
- File Browser
- Classifications
- CWE-269, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.63.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory proxy-auth account provisioning PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo