CVE-2026-54090
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFile Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.33.8, when a shell interpreter is configured (e.g. /bin/sh -c), the command allowlist can be bypassed through shell metacharacters. The allowlist validates only the first token of user input, but the entire raw string is handed to the shell — semicolons, pipes, backticks, and $() all work to chain arbitrary commands after a permitted one. This vulnerability is fixed in 2.33.8.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFile Browser versions before 2.33.8 have a command injection vulnerability when a shell interpreter is configured. The allowlist validates only the first token of user input but passes the entire raw string to the shell, allowing attackers to bypass the allowlist using shell metacharacters like semicolons, pipes, backticks, and $() to chain arbitrary commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify File Browser versionRun 'filebrowser --version' or check the version via your package manager, docker image tag, or binary you deployedAffected if Version is below 2.33.8 (e.g., 2.33.7, 2.32.0, etc.)
-
Locate configuration fileFind the File Browser configuration file (commonly config.json, settings.json, or in the .filebrowser directory under the data root)Affected if Configuration file exists and shell interpreter is enabled (look for 'shell' or 'interpreter' setting with a value such as '/bin/sh', '/bin/bash', etc.)
-
Inspect shell interpreter settingOpen the configuration file and search for a field that specifies a shell command or interpreter pathAffected if A shell interpreter (e.g., /bin/sh, /bin/bash) is explicitly configured rather than set to null or empty
-
Review command allowlist configurationLocate any 'commands', 'allowedCommands', or 'allowlist' field in the configuration and examine which commands are permittedAffected if A allowlist exists but accepts only basic commands (such as 'git', 'grep') without additional metacharacter filtering
-
Test for metacharacter handlingIf you have access to the File Browser interface or API, observe whether semicolons, pipes, backticks, or $() in a user input are processed or stripped before reaching the shellAffected if Shell metacharacters are not stripped and raw user input reaches the configured shell interpreter
You are affected if File Browser version is below 2.33.8 AND a shell interpreter is configured in the settings, regardless of allowlist configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to File Browser version 2.33.8 or later. If immediate upgrade is not possible, disable shell interpreter configuration or review input sanitization to block shell metacharacters.
2.33.8
- Identify the File Browser installation method (e.g., package manager, Docker, binary)
- Check the current installed version (typically via 'filebrowser --version' or package manager query)
- Upgrade to version 2.33.8 or later using the appropriate method for your installation
- If using a package manager, run the equivalent of 'apt update && apt install filebrowser' or 'brew upgrade filebrowser'
- If using Docker, pull the new image with the version tag (e.g., 'docker pull filebrowser/filebrowser:v2.33.8' or ':latest')
- If using a binary, download the new binary from the GitHub releases page and replace the existing binary
- Verify the upgrade was successful by checking the version number
- Restart the File Browser service to ensure the new version is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data