dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-55667

HIGH · 8.2 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 →
88/100
Remediation priority · High
Remotely reachable 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.16, a scoped, non-admin File Browser user holding only the Create permission can delete arbitrary files outside their scope (other tenants' data, and the application's own database) via the upload failure-cleanup path. ScopedFs.RemoveAll is the one dereferencing operation that skips the symlink guard every other method enforces. The direct-upload handler runs RemoveAll on the user-controlled path during failed-upload cleanup, gated only by Perm.Create. If an escaping directory symlink already exists inside the user's scope, an authenticated create-only user can delete an out-of-scope target, bypassing both the ScopedFs boundary and the Perm.Delete gate. This vulnerability is fixed in 2.63.16.

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

A path traversal vulnerability in File Browser before 2.63.16 allows scoped, non-admin users with only Create permission to delete arbitrary files outside their assigned scope. The ScopedFs.RemoveAll method skips the symlink guard that other methods enforce, and the direct-upload handler calls RemoveAll on a user-controlled path during failed-upload cleanup, bypassing both the ScopedFs boundary and the Perm.Delete gate.

MitigationUpgrade to File Browser version 2.63.16 or later, which adds the symlink guard to the RemoveAll method in the upload failure-cleanup path.

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

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

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. Check File Browser version
    Run 'filebrowser --version' or check the binary version (e.g., filebrowser -v). Alternatively, check the version reported in the admin UI dashboard or in the installed package metadata.
    Affected if version is below 2.63.16 (e.g., 2.63.15, 2.63.0, 2.62.0, etc.)
  2. Identify non-admin users with Create permission
    In File Browser admin panel, navigate to Users/Shares settings and review each user's permission set. Look for users marked as non-admin who have 'Create' permission enabled on any share.
    Affected if any non-admin user has the Create permission flag enabled on their scoped share
  3. Verify if direct upload handler is in use
    Check the File Browser configuration file (commonly config.json or settings file) for upload-related settings. The vulnerability triggers during failed-upload cleanup when the direct upload endpoint is used.
    Affected if direct upload functionality is enabled and users can trigger upload operations that may fail and trigger cleanup routines
  4. Confirm ScopedFs implementation
    If you have access to the source code or binary, inspect the ScopedFs.RemoveAll method to verify whether the symlink guard is present. In affected versions, this guard is missing, allowing path traversal outside the defined scope.
    Affected if the ScopedFs.RemoveAll method lacks symlink validation (symlink guard absent in code)
  5. Check file system permissions on shares
    Review the share definitions in File Browser configuration to determine if any shares allow access to directories that contain symlinks pointing outside the intended scope.
    Affected if shares have symlinks configured that point to directories outside the user's assigned scope

You are affected if running File Browser version below 2.63.16 and your deployment includes non-admin users with Create permission on scoped shares, as this combination enables the path traversal to delete files outside the assigned scope.

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 to File Browser version 2.63.16 or later, which adds the symlink guard to the RemoveAll method in the upload failure-cleanup path.

Recommended fix High confidence

2.63.16

  1. 1. Identify the current File Browser version by checking the application or package manager
  2. 2. Back up all user data, configuration files, and the application database before upgrading
  3. 3. Upgrade File Browser to version 2.63.16 or later
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Test that the Create permission no longer allows deletion of files outside the user's scoped directory

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55667 — 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-55667 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