# CVE-2026-53580: Trilium arbitrary file read and denial of service via file:// URLs in the automatic image-download feature

> Authenticated users can read arbitrary local files or crash the server via file:// URLs in image tags due to lack of path validation.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **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:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-3gxr-j6g6-q75c

## What is CVE-2026-53580?

CVE-2026-53580 is a high-severity path traversal vulnerability in TriliumNext Trilium, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Trilium is an open-source hierarchical note-taking application. In versions prior to 0.104.0, the automatic image-download feature accepts file:// URLs in a note's img tags and reads the referenced local file with no path validation, allowing any authenticated user to disclose arbitrary files readable by the Trilium process. When a text note is saved, Trilium scans its HTML for image sources and downloads each external one; because the HTML sanitizer keeps file as an allowed scheme, a source such as file:///etc/passwd is passed straight to a filesystem read and its contents are stored as a note attachment the user can then retrieve. Pointing the same primitive at an unbounded source such as /dev/zero causes uncontrolled memory allocation that crashes the server process. The feature is enabled by default and is reachable through the web UI, the ETAPI, the web clipper, and note imports, requiring only an authenticated session or an ETAPI token. This issue is fixed in version 0.104.0

Weakness: CWE-73 (External Control of File Name or Path), CWE-552 (Files or Directories Accessible to External Parties), CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Triliumnotes Trilium.

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

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

## Is CVE-2026-53580 being exploited?

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

## Other vulnerabilities in TriliumNext Trilium

- [CVE-2026-48996](https://insights.sbomify.com/CVE-2026-48996/): Trilium: Malicious import with GeoMap marker title XSS leads to RCE on the desktop client (critical 9.3)
- [CVE-2026-53578](https://insights.sbomify.com/CVE-2026-53578/): Trilium: Note Import to RCE via Mind Elixir dangerouslySetInnerHtml (critical 9.3)
- [CVE-2026-53579](https://insights.sbomify.com/CVE-2026-53579/): Trilium: Note Import to RCE via Book Note (critical 9.3)
- [CVE-2026-47727](https://insights.sbomify.com/CVE-2026-47727/): Code injection in Trilium (high 8.6)
- [CVE-2026-77438](https://insights.sbomify.com/CVE-2026-77438/): Trilium unauthenticated share-search discloses password-protected and hidden shared notes (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53580 is a high-severity path traversal vulnerability in TriliumNext Trilium, published on 27 Aug 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-53580 exists.

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

## Sources

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

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