Quick answers
- Is CVE-2026-53579 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53579 being exploited in the wild.
- How severe is CVE-2026-53579?
- Informational severity, with a CVSS score of 9.3, published 27 August 2026.
- Which products and versions are affected?
- TriliumNext Trilium up to and including 0.103.0.
- Is there a fix for CVE-2026-53579?
- A patch was published on 2026-08-27: fixed in version 0.104.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53579 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-53579?
- Check whether you run TriliumNext Trilium at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an HTML injection / cross-site scripting (XSS) that escalates to remote code execution on the desktop client. Root cause: the import sanitization function `processTextNoteContent()` is only called for notes with type "text", but book notes follow the same rendering path through `renderText()` and `content_renderer.getRenderedContent()`, where unsanitized content is injected into the page via jQuery's `.html()` method. Attack vector is local and requires user interaction (importing a malicious archive). On Electron-based desktop clients with `nodeIntegration` enabled, the injected JavaScript can call `require('child_process').exec()` to execute system commands. The vulnerability affects Trilium versions up to 0.103.0 and is fixed in 0.104.0.
Affected products
- TriliumNext Trilium up to and including 0.103.0
Timeline
- 2026-08-27: disclosed
- 2026-08-27: patched: fixed in version 0.104.0