Quick answers
- Is CVE-2026-77438 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77438 being exploited in the wild.
- How severe is CVE-2026-77438?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- TriliumNext Trilium up to and including 0.103.0.
- Is there a fix for CVE-2026-77438?
- A patch was published on 2026-07-13: Fix committed to main branch; version 0.104.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77438 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-77438?
- Check whether you run TriliumNext Trilium at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a broken access control (CWE-863) in the GET /share/api/notes search endpoint. The endpoint authorizes only the ancestor note supplied in the request, then performs a full-text search (including note content) across the entire published subtree without re-checking per-note shareCredentials or shareHiddenFromTree protections. An unauthenticated attacker can enumerate protected notes by their titles and paths, and use the endpoint as a boolean oracle to confirm arbitrary substrings of note content, recovering full contents of password-protected notes. The direct content routes enforce these controls via checkNoteAccess(), but the search endpoint bypasses this check. The vulnerability is fixed in version 0.104.0 by applying the same per-note authorization checks to search results.
Affected products
- TriliumNext Trilium up to and including 0.103.0
Timeline
- 2026-08-27: disclosed: Published in NVD
- 2026-07-13: patched: Fix committed to main branch; version 0.104.0 released