Nixpkgs security tracker

Login with GitHub

Details of issue NIXPKGS-2026-0945

NIXPKGS-2026-0945
published on
Permalink CVE-2026-34528
8.1 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 8 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package filebrowser-quantum
  • @LeSuisse removed package python312Packages.filebrowser-safe
  • @LeSuisse removed package python313Packages.filebrowser-safe
  • @LeSuisse removed package python314Packages.filebrowser-safe
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
File Browser's Signup Grants Execution Permissions When Default Permissions Includes Execution

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to version 2.62.2, the signupHandler in File Browser applies default user permissions via d.settings.Defaults.Apply(user), then strips only Admin. The Execute permission and Commands list from the default user template are not stripped. When an administrator has enabled signup, server-side execution, and set Execute=true in the default user template, any unauthenticated user who self-registers inherits shell execution capabilities and can run arbitrary commands on the server. This issue has been patched in version 2.62.2.

Affected products

filebrowser
  • ==< 2.62.2

Matching in nixpkgs

Ignored packages (4)

Package maintainers

Advisory: https://github.com/filebrowser/filebrowser/security/advisories/GHSA-x8jc-jvqm-pm3f