# CVE-2026-55498: FileRise Shared Folder Symlink Escape

> An unauthenticated attacker with a valid share token can access files outside the shared folder via symlink traversal in FileRise.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-83rw-5ffw-p798

## What is CVE-2026-55498?

CVE-2026-55498 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.15.0, FileRise public shared-folder links with subfolder browsing enabled can follow a symbolic link inside the shared folder to a sibling directory under the upload root. An unauthenticated holder of a valid share token can use shared-folder listing, direct download, or ZIP creation to access files outside the folder that was actually shared. The flaw occurs because the affected shared-folder paths resolve symlinks without enforcing the original shared folder as the real-path boundary. This issue is fixed in version 3.15.0.

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

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


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

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

## Is CVE-2026-55498 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55498 is a medium-severity path traversal vulnerability in error311 FileRise, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55498 exists.

Affected product: error311 FileRise. 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-55498/ (Markdown: https://insights.sbomify.com/CVE-2026-55498/index.md)
```

## Sources

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

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