CVE-2026-47727: Trilium: RCE via `shareTemplate` relation missing `isDangerous` flag — Safe import bypass leading to EJS SSTI (Incomplete Fix of CVE-2026-45668)
Trilium is an open-source hierarchical note-taking application. In versions prior to 0.104.0, the default-on "Safe import" filter fails to neutralize the shareTemplate relation because that relation is not marked as dangerous, allowing an attacker-supplied import archive to plant a server-side template that leads to remote code execution. The relation is omitted from the built-in list of dangerous attributes, so unlike other code-loading relations it is not disabled on import, and when the victim later publishes the imported note the public share renderer feeds the linked EJS code note's raw bytes into ejs.render, which compiles them in the server's Node process. An unauthenticated request to the shared note then executes the attacker's JavaScript with full access to require, process, the filesystem, and the network. This issue is fixed in version 0.104.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Triliumto a version that resolves this vulnerability.Fixed in 0.104.0
Event History
Frequently Asked Questions
Who is exposed to this issue?
Trilium instances running versions before 0.104.0 are exposed if a user imports an attacker-supplied archive and later publishes the imported note. The Safe import filter is enabled by default but does not prevent this attack path.
What must an attacker do to achieve code execution?
The attacker must provide a crafted import archive that uses the shareTemplate relation to link attacker-controlled EJS code. After the victim imports it and publishes the affected note, an unauthenticated request to that shared note triggers execution of the embedded JavaScript on the server.
What privileges does successful exploitation provide?
The attacker-supplied JavaScript executes in Trilium's server-side Node process. It has access to require, process, the filesystem, and the network.
What can be done if upgrading is not immediately possible?
Do not import untrusted archives, even when Safe import is enabled. Avoid publishing notes imported from untrusted sources, since publishing activates the vulnerable rendering path.