Security readout for executives and security teams
Plain-English summary
A malicious Trilium import can bypass the default Safe import protection. When a user opens the containing note, embedded script can run; on the desktop client, this can become full code execution on the user’s machine. Versions before 0.104.0 are affected.
Executive priority
Treat this as an urgent upgrade for affected desktop installations. A successful attack could compromise data, system integrity, and availability after a user opens imported content. Prioritize users who exchange or import Trilium archives from external parties.
Technical view
Safe import sanitizes HTML for text notes but not book notes. Unsanitized book-note content reaches the text-note rendering path and is inserted into grid previews through jQuery HTML rendering. Electron’s enabled Node integration turns renderer script injection into remote code execution on desktop clients.
Likely exposure
Exposure requires Trilium before 0.104.0 and user interaction with an attacker-supplied import archive. Desktop clients face the highest impact because script execution can reach Node capabilities. Browser-based use may still face cross-site scripting, but the supplied sources specifically associate full machine compromise with Electron.
Exploitation context
The supplied sources describe a malicious-import attack requiring the victim to import an archive and open its containing note. CVSS 4.0 rates it 9.3 with user interaction required. It is not listed as KEV, and the bundle provides no evidence of active exploitation.
Researcher notes
The trust-boundary failure combines incomplete type-specific sanitization with a shared unsafe rendering sink. CWE-79 covers the script injection; CWE-94 reflects desktop code-execution impact. The cited fix commit and advisory are the authoritative references. The bundle does not establish public exploitation, available indicators, or affected-version-specific telemetry.
Mitigation direction
- Upgrade Trilium to version 0.104.0 or later.
- Until upgraded, do not import archives from untrusted or unverifiable sources.
- Prioritize desktop clients because Electron Node integration enables machine-level code execution.
- Follow the vendor advisory for any additional operational guidance.
Validation and detection
- Inventory Trilium installations and identify every version below 0.104.0.
- Confirm upgraded clients report version 0.104.0 or later.
- Identify users who imported externally supplied archives while running affected versions.
- Review suspicious activity around imported book notes without opening potentially malicious content.
- Verify organizational workflows restrict untrusted Trilium archive imports.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53579 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/TriliumNext/Trilium/security/advisories/GHSA-h7w4-cjfg-cvj8CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/TriliumNext/Trilium/commit/abb01f09b3ad7792bd3d42a973730c99a062a808CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.