CVE-2026-53580
moderateAuthenticated Arbitrary File Read and DoS in Trilium Notes via file:// URLs
Trilium Notes, an open-source hierarchical note-taking application, in versions before 0.104.0 allows arbitrary local file disclosure and a denial-of-service through its automatic image-download feature. When a text note is saved, Trilium scans the HTML for image sources and downloads each external one; because the HTML sanitizer keeps file as an allowed scheme, an authenticated user can embed a source such as file:///etc/passwd, which is passed directly to a filesystem read with no path validation and stored as a note attachment the user can then retrieve. An attacker holding any authenticated session or ETAPI token gains read access to arbitrary files readable by the Trilium process, and can crash the server process by pointing the same primitive at an unbounded source such as /dev/zero, which drives uncontrolled memory allocation. All Trilium deployments running versions prior to 0.104.0 are affected; the feature is enabled by default and reachable through the web UI, the ETAPI, the web clipper, and note imports. No public proof-of-concept is known, the issue is not in CISA's KEV catalog, and EPSS currently assigns roughly a 0.3% probability of exploitation within 30 days, so no in-the-wild exploitation has been reported.
What to do: Upgrade all Trilium server deployments to version 0.104.0 or later. Until patched, restrict note-creation rights and ETAPI tokens to trusted users, minimize the local files readable by the Trilium process account, and audit existing note attachments for content pulled in via file:// image sources. Keep the instance off the public internet or behind a VPN where feasible, and consider disabling automatic image download if that option is available in your build.
| Trilium (open-source project) Trilium Notes | All versions prior to 0.104.0; fixed in 0.104.0 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
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, CWE-400, CWE-552
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
In the news0 stories
No ingested article mentions this CVE yet.