dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-35593

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 an open-source, cross-platform hierarchical note taking application for building large personal knowledge bases. Versions 0.102.1 and prior are vulnerable to Local File Inclusion, allowing an authenticated attacker to read sensitive arbitrary files from the server's filesystem. The uploadModifiedFileToAttachment function, which is called when a POST request is received to /api/attachments/{attachmentId}/upload-modified-file, replaces the content of the attachment with the content from another file (whose path is provided in filePath of Request body). After which the content of the attachment can be viewed at /api/attachments/{attachmentId}/download. This exposes sensitive system files such as SSH keys, credentials, configs, and OS files, potentially leading to remote code execution and compromise of co-hosted applications. This issue has been fixed in version 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 0.102.1 and prior contain a Local File Inclusion vulnerability in the uploadModifiedFileToAttachment function. When processing a POST request to /api/attachments/{attachmentId}/upload-modified-file, the function reads content from a filePath parameter in the request body without proper validation, allowing an authenticated attacker to read arbitrary files from the server filesystem by manipulating the filePath parameter.

MitigationUpgrade Trilium Notes to version 0.102.2 or later, which contains the fix for this vulnerability. If immediate upgrading is not feasible, consider restricting API access to trusted users only as a temporary mitigation.

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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N

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. Identify Trilium Notes installation
    Look for the Trilium application process, check for trilium-diagram.exe or trilium.exe process running, or locate trilium-data directory typically in user data folders
    Affected if Trilium Notes is installed and running
  2. Determine installed Trilium version
    Check the application's version information - typically accessible via the Trilium UI (Help > About) or check package.json/version file in the installation directory
    Affected if Version is 0.102.1 or lower (any version 0.102.1 and prior)
  3. Verify attachment upload API is accessible
    Test network access to the /api/attachments/* endpoints on the Trilium server port (default 3784) - check if the API responds to requests
    Affected if Attachment API endpoints are reachable and the application accepts API requests
  4. Confirm user authentication is configured
    Review Trilium authentication settings - check if the server has authentication enabled (local server authentication or other auth mechanisms)
    Affected if Authentication is enabled but the application has user accounts that could be compromised, or if authentication is disabled entirely

If Trilium Notes version 0.102.1 or prior is running and the attachment API is accessible to authenticated users, the environment is affected by this Local File Inclusion vulnerability.

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 Trilium Notes to version 0.102.2 or later, which contains the fix for this vulnerability. If immediate upgrading is not feasible, consider restricting API access to trusted users only as a temporary mitigation.

Recommended fix High confidence

0.102.2

  1. 1. Back up your Trilium Notes data directory and database before upgrading
  2. 2. Stop the Trilium Notes service or application
  3. 3. Download Trilium Notes version 0.102.2 from the official GitHub releases (github.com/zadam/trilium)
  4. 4. Install or extract version 0.102.2, replacing the previous installation
  5. 5. Start the Trilium Notes service or application
  6. 6. Verify the upgrade was successful by checking the application version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35593 — 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-35593 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