# CVE-2026-77438: Trilium unauthenticated share-search discloses password-protected and hidden shared notes

> Unauthenticated attackers can bypass password and visibility controls on shared notes via the search endpoint, disclosing protected content.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-6rxv-6w3q-7mv9

## What is CVE-2026-77438?

CVE-2026-77438 is a high-severity missing authorization vulnerability in TriliumNext Trilium, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Trilium is an open-source hierarchical note-taking application. In versions up to and including 0.103.0, the public share-search endpoint does not enforce the per-note shareCredentials and shareHiddenFromTree controls, allowing an unauthenticated visitor to read the titles, tree paths, and content of protected shared notes. The endpoint authorizes only the ancestor note supplied in the request and then runs a full-text search across the entire published subtree, returning each matching note's title, share identifier, and hierarchical path without re-checking whether that individual note requires a share password or is hidden from the navigation tree. Because the search matches note content, an attacker can enumerate protected notes and use the endpoint as a boolean oracle that confirms arbitrary substrings, recovering the full contents of notes that should be gated behind a password. This issue is fixed in version 0.104.0.

Weakness: CWE-863 (Incorrect Authorization), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-77438?

It affects 1 product.


Products: Triliumnotes Trilium.

## How do I fix CVE-2026-77438?

No fix has been published for CVE-2026-77438 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-77438 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77438 exists.

## Other vulnerabilities in TriliumNext Trilium

- [CVE-2026-48996](https://insights.sbomify.com/CVE-2026-48996/): Trilium: Malicious import with GeoMap marker title XSS leads to RCE on the desktop client (critical 9.3)
- [CVE-2026-53578](https://insights.sbomify.com/CVE-2026-53578/): Trilium: Note Import to RCE via Mind Elixir dangerouslySetInnerHtml (critical 9.3)
- [CVE-2026-53579](https://insights.sbomify.com/CVE-2026-53579/): Trilium: Note Import to RCE via Book Note (critical 9.3)
- [CVE-2026-47727](https://insights.sbomify.com/CVE-2026-47727/): Code injection in Trilium (high 8.6)
- [CVE-2026-53580](https://insights.sbomify.com/CVE-2026-53580/): Trilium arbitrary file read and denial of service via file:// URLs in the automatic image-download feature (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77438 and fix it if it is affected.

What it is: CVE-2026-77438 is a high-severity missing authorization vulnerability in TriliumNext Trilium, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77438 exists.

Affected product: TriliumNext Trilium. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77438/ (Markdown: https://insights.sbomify.com/CVE-2026-77438/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77438
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77438
- OSV: https://osv.dev/vulnerability/CVE-2026-77438

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77438/
Summaries are generated and may contain mistakes; the official description above is the record.