Skip to main content
VulnerabilityPublished

CVE-2026-39311: TriliumNext Trilium · Cross-site Scripting

Affects TriliumNext TriliumSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.102.2 when convenient.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.102.2
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade Trilium and triliumnext/Trilium to 0.102.2.

Affected software

ProductAffectedFixed in
TriliumNextTriliumAffected
  • <0.102.2
Fixed in
  • 0.102.2
GitHubtriliumnext/Triliumpkg:github/triliumnext/TriliumOther threatsAffected
  • <0.102.2
Fixed in
  • 0.102.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Trilium Notes to version 0.102.2 or later, where this vulnerability has been fixed. The fix addresses SVG sanitization and re-enables Content Security Policy protections. Until upgraded, avoid opening or sharing SVG attachments from untrusted sources. Patch status is confirmed fixed in version 0.102.2.

Description

Trilium Notes versions 0.102.1 and earlier contain a critical vulnerability due to lack of SVG sanitization combined with a disabled Content Security Policy and a publicly accessible backend API. This flaw allows an attacker to execute arbitrary Node.js code on the server by tricking an authenticated user into viewing a malicious SVG attachment. The vulnerability arises from serving SVGs without sanitization and disabling Helmet's CSP middleware, enabling script execution under the Same-Origin Policy. The issue is fixed in version 0.102.2.

References

Community reviews

Loading reviews…