dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2026-54096

HIGH · 8.4 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 →
89/100
Remediation priority · High
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.7, `POST /api/share/<path>` accepts an authenticated request for an arbitrary path and stores a public share record without checking whether the target file currently exists. Later, when a file is created at that same path, the previously created public share immediately becomes valid and exposes the new file through `GET /api/public/dl/<hash>`. This vulnerability is fixed in 2.63.7.

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

In File Browser versions prior to 2.63.7, the `POST /api/share/<path>` endpoint allows authenticated users to create public share records for arbitrary file paths WITHOUT verifying the target file currently exists. An attacker can pre-create a share for a path that doesn't exist yet; once a legitimate file is later created at that exact path, the share becomes immediately valid and exposes the new file via `GET /api/public/dl/<hash>`, bypassing normal access controls.

MitigationUpgrade File Browser to version 2.63.7 or later, which implements proper file existence validation before creating share records.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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 installed File Browser version
    Run `filebrowser --version` or check the version displayed in the web UI header. If using Docker, check the image tag or run `docker images` to see the versioned image.
    Affected if The installed version is any version prior to 2.63.7 (e.g., 2.63.6, 2.63.0, 2.62.0, etc.)
  2. Test share creation on non-existent path
    Send an authenticated POST request to `/api/share/<nonexistent_path>` where `<nonexistent_path>` is a file path that definitely does not exist in the File Browser storage. Check if the API returns a success response with a share hash.
    Affected if The API returns HTTP 200 (success) and provides a share hash for a path that does not exist, indicating no existence validation is performed.
  3. Inspect share storage for suspicious records
    Examine the File Browser database (typically a SQLite file like `filebrowser.db` or similar, check documentation for your installation) in the `shares` or similar table. Look for share records where the `path` value points to locations that may not have contained files at the time the share was created.
    Affected if Share records exist for paths where the corresponding files did not exist at share creation time, indicating the vulnerability is present or was exploited.

A user is affected if running any File Browser version below 2.63.7 AND the share API accepts share creation requests for paths that do not currently exist on the filesystem.

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.7 or later, which implements proper file existence validation before creating share records.

Recommended fix High confidence

2.63.7

  1. Identify the current version of File Browser being used
  2. Backup the File Browser configuration and data directory
  3. Upgrade File Browser to version 2.63.7 or later
  4. Verify the upgrade was successful by checking the version
  5. Test that the /api/share/<path> endpoint now properly validates file existence before creating shares
  6. Restart the File Browser service if necessary

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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