High Injection exploit reference

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.

Published Aug 27, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.7% (30-day exploitation probability)+8
Technical severity (high)+6
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.74%

ahead of 53% of scored CVEs · Oct 14, 2026

Affects

TriliumNext

Trilium

CVSS base

8.8

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (TriliumNext Trilium, Triliumnotes Trilium).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
Apply the fixed version or the patch documented under Remediation.
Exploitation requires user interaction: tighten email/web filtering and warn affected users.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
TriliumNext	Trilium	version 0.104.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Triliumnotes	Trilium	< 0.104.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
8.6	CVSS 4.0	High	—	—	security-advisories@github.com via NIST National Vulnerability Database
8.6	CVSS 4.0	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP
8.8	CVSS 3.1	High	2.8	5.9	nvd@nist.gov via NIST National Vulnerability Database

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-94 · Code Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · triliumnext/trilium
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 14, 2026
Fix documented
Oct 14, 2026 · NIST National Vulnerability Database
Affected products added · triliumnotes/trilium
Oct 14, 2026 · NIST National Vulnerability Database
CVSS changed · 8.8
Oct 14, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
CVE published
Aug 27, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

2 on the record

github.com/TriliumNext/Trilium/security/advisories/GHSA-c26q-6pwv-wf25
Exploit, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
github.com/TriliumNext/Trilium/commit/0db3d4403ab26de13d19a8739f014ee72b716239
Patch, x_refsource_MISC, NIST National Vulnerability Database

Elsewhere on this site

TriliumNext
every CVE for this vendor

Injection
same class

CWE-94
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-77438 Trilium unauthenticated share-search discloses password-protected and hidden shared notes Aug 27, 2026
Medium CVE-2026-53579 Trilium: Note Import to RCE via Book Note Aug 27, 2026
High CVE-2026-53580 Trilium arbitrary file read and denial of service via file:// URLs in the automatic image-download feature Aug 27, 2026
Medium CVE-2026-53578 Trilium: Note Import to RCE via Mind Elixir dangerouslySetInnerHtml Aug 27, 2026
Medium CVE-2026-48996 Trilium: Malicious import with GeoMap marker title XSS leads to RCE on the desktop client Aug 27, 2026
Critical CVE-2026-45668 Trilium Notes : Note Import to RCE via #docName Path Traversal (Safe Import Enabled) May 29, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-47727 is "Trilium: RCE via `shareTemplate` relation missing `isDangerous` flag — Safe import bypass leading to EJS SSTI (Incomplete Fix of CVE-2026-45668)", rated High. It affects Trilium (TriliumNext); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.74% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.