Trilium Notes EUVD-2026-33376

Exploitation requires the victim to use the Trilium desktop (Electron) client at a version below 0.102.2, to import an attacker-supplied ZIP archive through the application's Import feature with safe import enabled, and to subsequently navigate to or trigger the malicious launcher/doc note whose #docName label contains a ../ path-traversal sequence pointing at a payload code note (type: code, mime: text/plain) carrying raw HTML/JavaScript. Full RCE escalation specifically depends on the Electron renderer being configured with nodeIntegration enabled, which is the default for the desktop client; web/server-only deployments without an Electron renderer would face XSS and traversal impact but not direct host code execution. The CVSS UI:A (Active user interaction) and AV:L vector confirm the import-and-trigger user action is mandatory - there is no remote unauthenticated exploitation path.

Signals are mixed and require careful interpretation. The CVSS 4.0 vector is AV:L/AC:L/AT:N/PR:N/UI:A with high confidentiality, integrity, availability, and subsequent-system impact - note that AV:L (Local) combined with UI:Active reflects that the attacker must deliver a ZIP file and the user must import it with safe import enabled, not that the attacker needs prior local access. EPSS and KEV data are not provided, and there is no public exploit identified at time of analysis, so this is not currently a mass-exploitation candidate. However, the technical impact is severe (full RCE via Electron nodeIntegration) and the social-engineering barrier is low: importing notes is a routine workflow for Trilium users, especially when migrating knowledge bases. Real-world risk is meaningful for targeted attacks against researchers, journalists, or developers who exchange note archives, but lower for typical drive-by exploitation.

An attacker shares what appears to be a useful Trilium knowledge-base archive (e.g., a research notes export) with the victim via email, chat, or a forum. The victim opens Trilium and uses Import with safe import enabled; the archive plants a payload code note containing JavaScript and a launcher/doc note whose #docName label traverses (../) to the payload's API endpoint, executing the script in the Electron renderer with Node.js privileges and yielding shell access on the victim's host.