CVE-2026-54096: File Browser Improper Access Control Occurs Vulnerability
HIGHCVE-2026-54096 is a HIGH (CVSS 8.4) improper access control occurs vulnerability (CWE-668: Exposure of Resource to Wrong Sphere) affecting File Browser libraries in the Go ecosystem. The issue involves improper access control occurs via pre-created public share for a non-existent path. Remediation is available by upgrading affected packages to version 2.63.7.
CVE-2026-54096 at a Glance
Security Impact
CVSS: 8.4
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
How to Fix CVE-2026-54096
To remediate this vulnerability, upgrade all affected File Browser dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.7
Upgrade github.com/filebrowser/filebrowser to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/filebrowser/filebrowser/v2
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-54096, inspect your project dependencies for File Browser:
inspect dependencies for github.com/filebrowser/filebrowser/v2
Analyze the terminal output to locate any version of File Browser in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.63.7), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-668: Exposure of Resource to Wrong Sphere, where the product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. In File Browser, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-54096 Affected File Browser Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/filebrowser/filebrowser/v2
|
Go |
< 2.63.7
|
2.63.7
|
|
github.com/filebrowser/filebrowser
|
Go |
≤ 1.11.0
|
|
References
Frequently Asked Questions
What is CVE-2026-54096?
Which File Browser versions are affected?
What version fixes CVE-2026-54096?
Is github.com/filebrowser/filebrowser/v2 affected?
Is github.com/filebrowser/filebrowser affected?
What is the CVSS score of CVE-2026-54096?
What CWE is associated with CVE-2026-54096?
How can I check Go dependencies for CVE-2026-54096?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-3q2p-72cj-682c",
"modified" : "2026-07-21T14:45:00Z",
"published" : "2026-06-12T21:07:55Z",
"aliases" : [ "CVE-2026-54096" ],
"summary" : "File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path",
"details" : "### Summary\nThis is similar vulnrability of **`CVE-2026-0035`**, which was fixed in Android `MediaProvider` with **high** severity. In the original Java issue, `MediaStore.createWriteRequest()` accepted attacker-controlled URIs and created a future grant even when the referenced media item did not exist yet. The Android fix added an existence check before creating the request.\n\n`filebrowser/filebrowser` has the analogous issue in Go. `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>`.\n\n### Details\nThe vulnerable create path is:\n\n- `http/share.go`\n- `sharePostHandler()`\n- route: `POST /api/share/<path>`\n\n`sharePostHandler()` only checks that the caller is authenticated and has share/download permissions. It then builds a `share.Link` directly from `r.URL.Path` and saves it:\n\n```go\ns = &share.Link{\n Path: r.URL.Path,\n Hash: str,\n Expire: expire,\n UserID: d.user.ID,\n PasswordHash: string(hash),\n Token: token,\n}\n\nif err := d.store.Share.Save(s); err != nil {\n return http.StatusInternalServerError, err\n}\n```\n\nThere is no `Stat`, `Exists`, or equivalent check before the public share record is committed.\n\nThe vulnerable consume path is:\n\n- `http/public.go`\n- `withHashFile()`\n- routes: `GET /api/public/share/<hash>`, `GET /api/public/dl/<hash>`\n\nEach public request loads the saved share by hash and then resolves `link.Path` against the owner's current filesystem state:\n\n```go\nfile, err := files.NewFileInfo(&files.FileOptions{\n Fs: d.user.Fs,\n Path: link.Path,\n ...\n})\n```\n\nThis means the share is not bound to an object that existed at creation time. It is bound only to a path string, so a share created for a nonexistent path becomes valid later as soon as that path is populated.\n\n\n### PoC\nThe PoC below starts from external HTTP input only.\n\n1. Authenticate to File Browser.\n2. Confirm `/future4.txt` does not exist.\n3. Create a public share for `/future4.txt` anyway.\n4. Confirm the public share returns `404`.\n5. Upload a file to `/future4.txt`.\n6. Reuse the same public share URL and read the file content.\n\nReproduction commands:\n\n```bash\nTOKEN=$(curl -s -X POST http://127.0.0.1:8091/api/login \\\n -H 'Content-Type: application/json' \\\n -d '{\"username\":\"admin\",\"password\":\"Password123!\"}')\n\ncurl -i -X POST http://127.0.0.1:8091/api/share/future4.txt \\\n -H \"X-Auth: $TOKEN\" \\\n -H 'Content-Type: application/json' \\\n -d '{}'\n\ncurl -i http://127.0.0.1:8091/api/public/dl/JVeEQlLO\n\ncurl -i -X POST http://127.0.0.1:8091/api/resources/future4.txt \\\n -H \"X-Auth: $TOKEN\" \\\n --data-binary 'fourth-secret'\n\ncurl -i http://127.0.0.1:8091/api/public/dl/JVeEQlLO\n```\n\n\n### Impact\nAn authenticated user can create a public share for a path before the file exists, and that same share later exposes whatever file is created at that path. This can unintentionally publish future sensitive files and bypass the expected invariant that a share grants access only to an existing object reviewed at creation time.\n\n### Reference\n\nOriginal CVE: https://nvd.nist.gov/vuln/detail/CVE-2026-0035",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/filebrowser/filebrowser/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.63.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.63.6"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/filebrowser/filebrowser"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.11.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/filebrowser/filebrowser/security/advisories/GHSA-3q2p-72cj-682c"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54096"
}, {
"type" : "WEB",
"url" : "https://github.com/filebrowser/filebrowser/commit/166583db632e088e9f0adce30aec43bb9d9019f4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/filebrowser/filebrowser"
}, {
"type" : "WEB",
"url" : "https://github.com/filebrowser/filebrowser/releases/tag/v2.63.7"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-367", "CWE-668", "CWE-863" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-12T21:07:55Z",
"nvd_published_at" : "2026-06-25T19:16:41Z"
}
}