# CVE-2026-90930: File Browser through 2.63.23 Path Traversal via Symlink Alias

> Authenticated users can bypass file access restrictions and read or modify protected files by exploiting symbolic link resolution flaws in File Browser.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-7w29-q235-57m9, GHSA-w8fw-cw5v-v789

## What is CVE-2026-90930?

CVE-2026-90930 is a high-severity path traversal vulnerability in filebrowser, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File Browser through 2.63.23 applies path rules to the requested lexical path but resolves symbolic links without reapplying rules to the target, allowing authenticated users to bypass deny rules. Attackers can read and overwrite rule-denied files by accessing them through in-scope symbolic link aliases that resolve to denied paths.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-90930?


## How do I fix CVE-2026-90930?

No fix has been published for CVE-2026-90930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90930 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90930 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90930 and fix it if it is affected.

What it is: CVE-2026-90930 is a high-severity path traversal vulnerability in filebrowser, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90930 exists.

Affected product: filebrowser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90930/ (Markdown: https://insights.sbomify.com/CVE-2026-90930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90930
- OSV: https://osv.dev/vulnerability/CVE-2026-90930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90930/
Summaries are generated and may contain mistakes; the official description above is the record.