dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-54094

HIGH · 7.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

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 · unedited
File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.14, it does not stop the HTTP file handlers from following symbolic links before they open, serve, write, share, or list a file. As a result, a scoped user — and in some cases an unauthenticated public-share recipient — can cross the intended scope boundary by following a symlink whose path is lexically inside their scope but whose target is outside it. This vulnerability is fixed in 2.63.14.

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 confidence

File Browser versions prior to 2.63.14 contain a symbolic link traversal vulnerability where HTTP file handlers follow symlinks before performing file operations (open, serve, write, share, list). This allows scoped users or unauthenticated public-share recipients to access files outside their intended directory boundary by creating symlinks pointing to files outside the permitted scope.

MitigationUpgrade File Browser to version 2.63.14 or later, which implements symlink validation before file operations to prevent traversal beyond the configured scope.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed File Browser version
    Run the version command for File Browser (typically 'filebrowser --version' or check the binary metadata) and note the exact version number
    Affected if The installed version is lower than 2.63.14 (e.g., 2.63.13, 2.62.0, etc.)
  2. Confirm HTTP file handlers are in use
    Check if the File Browser HTTP service is running and accessible (inspect running processes or service configuration for filebrowser binary serving on HTTP/HTTPS ports)
    Affected if HTTP file handlers are active and the service is reachable over the network
  3. Verify user scoping configuration
    Inspect File Browser users.json or database for user definitions - look for users with scoped directories (not full filesystem access) or public share configurations
    Affected if There are scoped users with limited directory access or public share links are enabled
  4. Check for existing symlinks in user-accessible directories
    Examine directories accessible to scoped users or public shares for symbolic links (use 'ls -la' or similar file listing commands on scoped directories)
    Affected if Symlinks exist within scoped directories pointing to paths outside the user's allowed scope (e.g., symlink in a user's folder pointing to /root, /etc, or parent directories)

You are affected if File Browser version is below 2.63.14 AND HTTP file handlers are active AND scoped users or public shares exist in your configuration, as this combination allows symlink traversal outside the intended directory boundary.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade File Browser to version 2.63.14 or later, which implements symlink validation before file operations to prevent traversal beyond the configured scope.

Recommended fix High confidence

2.63.14

  1. Check the current installed version of File Browser using: filebrowser --version or filebrowser -v
  2. Stop the File Browser service if running
  3. Update to version 2.63.14. If using a package manager, run: apt update && apt install filebrowser (Debian/Ubuntu) or yum update filebrowser (RHEL/CentOS). If using Docker, pull the new image: docker pull filebrowser/filebrowser:v2.63.14
  4. If installing from binary, download from GitHub releases: curl -L -o filebrowser.tar.gz https://github.com/filebrowser/filebrowser/releases/download/v2.63.14/linux-amd64-filebrowser.tar.gz and extract the binary
  5. Verify the installation: filebrowser --version should show 2.63.14 or higher
  6. Restart the File Browser service
  7. Test that symbolic links outside the scoped directory are no longer accessible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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