CVE-2026-48996 TriliumNext CVE debrief

Who should care

Defenders responsible for systems using Trilium, especially those using the desktop client, should assess exposure and prioritize updating to version 0.104.0 or later. Monitoring for suspicious import activities and implementing compensating controls are also recommended.

Why it matters

CVE-2026-48996 is a critical vulnerability in Trilium that allows script injection and remote code execution. Defenders should assess exposure, prioritize updates, and monitor for suspicious activities.

• Cross-site scripting in GeoMap views
• Remote code execution in desktop clients due to enabled Node integration
• Potential for attacker-supplied scripts to execute on victim machines
• Need for verification of affected versions and remediation status

Technical summary

The Trilium application, up to and including version 0.103.0, has a vulnerability in its 'Safe import' feature. The feature does not properly sanitize note titles, and the GeoMap view renders these titles as raw HTML. This allows an attacker to inject malicious scripts into the application, leading to cross-site scripting and, in the case of the desktop client, remote code execution. Affected product deployments should be identified and owners assigned for follow-up. The vulnerability is caused by improper sanitization of note titles during the import process and improper rendering of titles in the GeoMap view, which can lead to cross-site scripting and remote code execution if exploited.

Defensive priority

Immediate attention is required for systems using Trilium versions up to 0.103.0. Users should update to version 0.104.0 or later to mitigate this vulnerability. Inventory checks and monitoring for suspicious import activities are recommended.

Recommended defensive actions

• Update Trilium to version 0.104.0 or later
• Inventory and assess exposure of Trilium installations
• Monitor for suspicious import activities
• Implement compensating controls for cross-site scripting and remote code execution
• Review and verify affected Trilium deployments in managed environments
• Track exceptions and retest remediated Trilium assets
• Check relevant monitoring, detection, and logs for exposed Trilium assets

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its critical severity and CVSS score of 9.3. The vulnerability is caused by improper sanitization of note titles during the import process and improper rendering of titles in the GeoMap view.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.