CVE-2026-47727

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 27, 2026
Fix named in the CVE record. Sources: github, github_commit.
GitHub commit

commit 0db3d4403ab2 (TriliumNext/Trilium)

Fix landed in TriliumNext/Trilium commit 0db3d4403ab2 — awaiting tagged release

https://github.com/TriliumNext/Trilium/commit/0db3d4403ab26de13d19a8739f014ee72b716239
GitHub advisoryMentions a patch (unverified)

Authenticated RCE in TriliumNext/Trilium via `shareTemplate` Relation — SafeImport Bypass → EJS SSTI (Safe import enable) · Advisory · TriliumNext/Trilium · GitHub

https://github.com/TriliumNext/Trilium/security/advisories/GHSA-c26q-6pwv-wf25

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-10-12 16:01 UTCEG score recompute
  4. 2026-10-11 19:44 UTCEG score recompute
  5. 2026-10-11 16:59 UTCEG score recompute
  6. 2026-10-11 14:23 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-10 01:53 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-10-09 03:03 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-08 01:18 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-06 19:15 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-05 18:59 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-05 07:19 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-03 19:21 UTCEG score recompute
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-02 19:17 UTCEG score recompute
  24. 2026-10-01 19:52 UTCEG score recompute
  25. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
Show 61 more
  1. 2026-09-30 19:54 UTCEG score recompute
  2. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-09-30 04:59 UTCEG score recompute
  4. 2026-09-29 08:55 UTCEG score recompute
  5. 2026-09-28 21:14 UTCEG score recompute
  6. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-09-27 18:25 UTCEG score recompute
  8. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-09-26 18:42 UTCEG score recompute
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-09-24 19:40 UTCEG score recompute
  13. 2026-09-23 20:18 UTCEG score recompute
  14. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-09-22 20:57 UTCEG score recompute
  16. 2026-09-21 21:29 UTCEG score recompute
  17. 2026-09-20 22:08 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-09-19 22:46 UTCEG score recompute
  20. 2026-09-18 23:24 UTCEG score recompute
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-09-18 00:03 UTCEG score recompute
  23. 2026-09-17 00:20 UTCEG score recompute
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-09-16 12:39 UTCEG score recompute
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  27. 2026-09-15 13:18 UTCEG score recompute
  28. 2026-09-14 02:15 UTCEG score recompute
  29. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-09-12 15:12 UTCEG score recompute
  31. 2026-09-11 15:50 UTCEG score recompute
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-09-10 16:27 UTCEG score recompute
  34. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  35. 2026-09-09 00:40 UTCEG score recompute
  36. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-08 02:46 UTCEG score recompute
  38. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-07 01:01 UTCEG score recompute
  40. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  41. 2026-09-06 01:38 UTCEG score recompute
  42. 2026-09-04 14:33 UTCEG score recompute
  43. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-09-02 15:37 UTCEG score recompute
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  46. 2026-09-01 15:58 UTCEG score recompute
  47. 2026-09-01 15:03 UTCEG score recompute
  48. 2026-09-01 14:31 UTCEG score recompute
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  50. 2026-08-31 03:15 UTCEG score recompute
  51. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  52. 2026-08-30 03:54 UTCEG score recompute
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  54. 2026-08-29 04:28 UTCEG score recompute
  55. 2026-08-29 04:07 UTCEG score recompute
  56. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  57. 2026-08-28 20:43 UTCEG score recompute
  58. 2026-08-28 19:47 UTCEG score recompute
  59. 2026-08-27 20:27 UTCEG score recompute
  60. 2026-08-27 20:16 UTCEG score recomputeFirst assessed: 8.6 HIGH
  61. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47727?
CVE-2026-47727 is a high-severity vulnerability; its CVE record was published on August 27, 2026. 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…
When was the CVE record for CVE-2026-47727 published?
The CVE record for CVE-2026-47727 was published on August 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-47727 actively exploited?
CVE-2026-47727 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47727?
CVE-2026-47727 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47727?
The CVE record for CVE-2026-47727 names the fix: "This issue is fixed in version 0.104.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47727

Explore →

Is Your Infrastructure Affected by CVE-2026-47727?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.