⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.8

How to Fix CVE-2026-35593: Path Traversal in Trilium

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 6.8 - Medium
Actively exploited?Not currently listed in CISA KEV
Affected< 0.102.2
Fixed inversion
Type (CWE)CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

What is CVE-2026-35593?

CVE-2026-35593 is a path traversal flaw in Trilium. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: 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.

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of Trilium that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open Trilium's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-35593

  1. Read the vendor advisory in full: https://github.com/TriliumNext/Trilium/security/advisories/GHSA-hf4x-22rg-pjjp
  2. Upgrade Trilium to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

<!-- enrich-agent-8 -->

Patch via your OS package manager

Vendor advisory (always check this first for exact fixed version and any

prerequisites): https://github.com/TriliumNext/Trilium/security/advisories/GHSA-hf4x-22rg-pjjp


# Debian / Ubuntu: pull the patched build of trilium from your distro repository.
sudo apt update
sudo apt install --only-upgrade trilium

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade trilium

# openSUSE
sudo zypper update trilium

# Verify the running version matches the fixed-in version (0.102.2).
trilium --version || dpkg -s trilium | grep -i version || rpm -q trilium


# Windows: pull the latest cumulative updates that include this CVE's fix.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

# If a specific KB is referenced in the advisory, install it directly.
# Get-WindowsUpdate -KBArticleID KBxxxxxxx -AcceptAll -Install -AutoReboot

Verify the fix landed


# Vendor advisory: https://github.com/TriliumNext/Trilium/security/advisories/GHSA-hf4x-22rg-pjjp
# 1. Confirm the running version matches the fixed-in version listed above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag this CVE on the patched target.

# 3. Inspect recent service / kernel logs for crash-loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

<!-- enrich-agent-8 -->

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-35593 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-35593?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Trilium run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*