CVE-2026-53579

Awaiting Analysis Awaiting Analysis - Queue

Stored XSS in Trilium Notes via Unsanitized Book Content

Publication date: 2026-08-27

Last updated on: 2026-09-09

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-09-09

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-53579

Affected Vendors & Products

Vendor	Product	Version / Range
trilium	trilium	to 0.103.0 (inc)
trilium	trilium	0.104.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-79	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-94	The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Attack-Flow Graph

Executive Summary

CVE-2026-53579 is a critical remote code execution (RCE) vulnerability in Trilium desktop applications affecting versions up to 0.103.0. The flaw allows attackers to bypass HTML sanitization during import by using a book note type, which is not sanitized unlike text notes. When a malicious note file with a book note containing HTML/JavaScript payloads is imported, the content is rendered unsanitized in grid view. The Electron renderer's Node integration enables the payload to execute arbitrary code.

The vulnerability requires user interaction to import a malicious file but no additional privileges. It escalates from cross-site scripting to full RCE on the victim's machine due to Node integration in the desktop client.

Detection Guidance

Check if your Trilium version is 0.103.0 or earlier. If so, the vulnerability may be present. Look for suspicious book notes or imported ZIP files containing HTML/JavaScript payloads. Review logs for unexpected script executions or system commands.

Impact Analysis

If exploited, this vulnerability allows attackers to execute arbitrary code on your system, such as running commands like opening a calculator or accessing sensitive files. It requires you to import a malicious note file, but once triggered, it can compromise confidentiality, integrity, and availability of your system and connected systems.

Compliance Impact

This vulnerability could lead to unauthorized code execution on affected systems, potentially exposing sensitive data. For GDPR, it may result in data breaches requiring notification under Articles 33-34. For HIPAA, it could compromise protected health information integrity and confidentiality, violating Security Rule requirements.

Mitigation Strategies

Upgrade Trilium to version 0.104.0 or later immediately. Avoid importing untrusted ZIP files. Disable Node integration in the Electron renderer if possible. Monitor for unusual activity after importing files.

Hi! I’m here to help you understand CVE-2026-53579. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70