dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-45668

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Trilium Notes is a cross-platform, hierarchical note taking application focused on building large personal knowledge bases. Prior to 0.102.2, a malicious ZIP archive imported with safe import enabled achieves RCE via #docName path traversal and XSS by combining a payload note (type: code, mime: text/plain) containing raw HTML/JS and a trigger note (type: doc or type: launcher) with a #docName label that uses ../ path traversal to point at the payload note's API endpoint. The desktop client Electron renderer runs with nodeIntegration enabled, so an RCE is triggered once the payload is executed. This vulnerability is fixed in 0.102.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Trilium Notes versions prior to 0.102.2 contain a path traversal vulnerability in the ZIP archive import feature that allows RCE. An attacker crafts a malicious ZIP containing a payload note with raw HTML/JS code and a trigger note using ../ path traversal in its #docName to point to the payload's API endpoint. Since the Electron desktop client renderer runs with nodeIntegration enabled, executing the trigger note results in arbitrary code execution.

MitigationUpgrade to Trilium Notes version 0.102.2 or later. Additionally, disable nodeIntegration and enable contextIsolation in the Electron configuration to prevent renderer process RCE vulnerabilities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Trilium Notes version
    Open Trilium Notes, go to Options > About, or check the package.json/installed application metadata to find the exact version number
    Affected if Version is below 0.102.2 (e.g., 0.102.1, 0.102.0, earlier releases)
  2. Verify safe import setting
    In Trilium Notes, navigate to Options > Import > ZIP and check whether 'safe import' is enabled. This setting is found in the import configuration panel.
    Affected if Safe import is turned ON (the vulnerability exploits safe import being enabled)
  3. Inspect Electron nodeIntegration setting
    If using the Trilium desktop client (Electron-based), check the main process configuration for nodeIntegration. This is typically in the Electron app initialization code or packaged config.
    Affected if nodeIntegration is set to true in the Electron renderer process configuration

User is affected if running Trilium Notes version below 0.102.2, with safe import enabled in ZIP import settings, and using the Electron desktop client with nodeIntegration enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Trilium Notes version 0.102.2 or later. Additionally, disable nodeIntegration and enable contextIsolation in the Electron configuration to prevent renderer process RCE vulnerabilities.

Recommended fix High confidence

0.102.2

  1. 1. Backup your Trilium Notes data directory before performing any upgrade
  2. 2. Download Trilium Notes version 0.102.2 or later from the official GitHub releases page (https://github.com/zadam/trilium/releases)
  3. 3. For the desktop client: uninstall the current version and install the new 0.102.2+ version
  4. 4. For the server version: stop the Trilium service, replace the application files with version 0.102.2+, and restart the service
  5. 5. Verify the upgrade was successful by checking the application version in the Help > About section
  6. 6. After upgrading, exercise caution with ZIP file imports from untrusted sources, even with safe import enabled

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,024.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45668 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45668 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data