# CVE-2026-53579: Trilium: Note Import to RCE via Book Note

> Attackers can achieve remote code execution on the victim's machine by importing a malicious note archive that bypasses sanitization in the desktop client.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-h7w4-cjfg-cvj8

## What is CVE-2026-53579?

CVE-2026-53579 is a critical code injection vulnerability in TriliumNext Trilium, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Trilium is an open-source hierarchical note-taking application. In versions up to and including 0.103.0, the default-on "Safe import" filter sanitizes HTML only for text notes and excludes the book note type, whose content is stored without sanitization and later rendered as HTML, allowing an attacker-supplied import archive to embed a payload that executes as script. A book note's content is routed through the same rendering path as text notes and injected into the page with jQuery's html method when the note is shown as a grid-view preview card, so a malicious note survives Safe import and runs as soon as the victim opens the containing note. On the desktop client the Electron renderer runs with Node integration enabled, so the injected JavaScript escalates from cross-site scripting to full remote code execution on the victim's machine. This issue is fixed in version 0.104.0.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-53579?

It affects 1 product.


Products: Triliumnotes Trilium.

## How do I fix CVE-2026-53579?

No fix has been published for CVE-2026-53579 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53579 being exploited?

There is no known exploitation of CVE-2026-53579 in the wild and no public exploit code.

## Other vulnerabilities in TriliumNext Trilium

- [CVE-2026-48996](https://insights.sbomify.com/CVE-2026-48996/): Trilium: Malicious import with GeoMap marker title XSS leads to RCE on the desktop client (critical 9.3)
- [CVE-2026-53578](https://insights.sbomify.com/CVE-2026-53578/): Trilium: Note Import to RCE via Mind Elixir dangerouslySetInnerHtml (critical 9.3)
- [CVE-2026-47727](https://insights.sbomify.com/CVE-2026-47727/): Code injection in Trilium (high 8.6)
- [CVE-2026-53580](https://insights.sbomify.com/CVE-2026-53580/): Trilium arbitrary file read and denial of service via file:// URLs in the automatic image-download feature (high 8.1)
- [CVE-2026-77438](https://insights.sbomify.com/CVE-2026-77438/): Trilium unauthenticated share-search discloses password-protected and hidden shared notes (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53579 and fix it if it is affected.

What it is: CVE-2026-53579 is a critical code injection vulnerability in TriliumNext Trilium, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-53579 in the wild and no public exploit code.

Affected product: TriliumNext Trilium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53579/ (Markdown: https://insights.sbomify.com/CVE-2026-53579/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53579
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53579
- OSV: https://osv.dev/vulnerability/CVE-2026-53579

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53579/
Summaries are generated and may contain mistakes; the official description above is the record.