CVE-2026-39311
MediumCVSS 6.8Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
Trilium Notes version 0.102.1 and prior contain a critical vulnerability allowing unauthenticated remote code execution (RCE). Lack of SVG sanitization combined with a disabled Content Security Policy (CSP) and a publicly reachable backend execution API allows an attacker to execute arbitrary Node.js code on the server by tricking an authenticated user into viewing a malicious SVG attachment.
Risk Assessment
The organization risks complete compromise of the Trilium Notes server, potentially leading to data theft, note modification, or further attacks on the infrastructure.
Recommendation
Immediately update Trilium Notes to version 0.102.2 or later, which includes a fix.
Other vulnerabilities in Trilium Notes
See all- CVE-2026-45668Critical
Trilium Notes is a cross-platform hierarchical note-taking application. Prior to version 0.102.2, a malicious ZIP archive imported with safe import enabled achieves RCE via #docName path traversal and XSS. It combines a payload note (type: code, mime: text/plain) containing raw HTML/JS and a trigger note (type: doc or launcher) with a #docName label using ../ path traversal to point at the payload note's API endpoint. The desktop client Electron runs with nodeIntegration enabled, so RCE is triggered once the payload is executed. This vulnerability is fixed in version 0.102.2.
- CVE-2026-91021Medium
Trilium Notes version v0.103.0 and earlier contains a stored cross-site scripting (XSS) vulnerability in the share renderer for webView notes due to improper HTML escaping of user-controlled #webViewSrc values. This vulnerability allows attackers with note-authoring privileges to inject arbitrary JavaScript that executes for any user who opens the shared note, including administrators.
- CVE-2026-45733High
Trilium Notes, a hierarchical note-taking application, has an XSS vulnerability in the #iconClass value, which is inserted without HTML attribute encoding. A stored payload can execute automatically when a victim opens a new tab or uses Ctrl+J, and due to enabled nodeIntegration and disabled contextIsolation in Electron, it can run operating-system commands. The issue is fixed in version 0.103.0.
- CVE-2026-39310High
Trilium Notes versions 0.102.1 and prior, when running in an Electron environment, disables authentication for the Clipper API, allowing unauthenticated attackers on the local network to access API endpoints without password, API token, or CSRF protection. An attacker can scan ports and gain unauthorized access to data, as well as conduct phishing or compromise the local system.
- CVE-2026-39309Medium
Trilium Notes versions 0.102.1 and prior contain a vulnerability to TCC bypass via prompt spoofing in the Electron configuration. A local attacker can run malicious code under the trusted app's identity using the RunAsNode flag to execute arbitrary system commands, leading to misleading macOS permission prompts and access to protected resources.
- CVE-2026-35593Medium
Trilium Notes versions up to 0.102.1 are vulnerable to Local File Inclusion (LFI). An authenticated attacker can read arbitrary files from the server's filesystem via the uploadModifiedFileToAttachment function.
Original NVD description (English source)
Trilium Notes is a cross-platform, hierarchical note taking application focused on building large personal knowledge bases. Versions 0.102.1 and prior contain a critical security flaw where lack of SVG sanitization combined with a disabled Content Security Policy (CSP) and a publicly reachable backend execution API results in an unauthenticated Remote Code Execution (RCE). The vulnerability arises from an insecure-by-design architecture: Trilium serves SVG attachments with the image/svg+xml MIME type without any sanitization, and it explicitly disables Helmet's Content Security Policy middleware, removing the primary defense against script execution in served assets. Because the malicious SVG runs under the Same-Origin Policy, it can issue a fetch('/') to extract the csrfToken from the document body. With that token, it can send a signed request to /api/script/exec to execute arbitrary Node.js code on the server. An attacker can compromise the entire server instance simply by tricking an authenticated user into viewing a shared SVG attachment. The issue has been fixed in version 0.102.2.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS