CVE-2026-77438

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd 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
7.5EG
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.4%CVSS: 7.5Exploit: 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 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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 49fc7b67d9d4 (TriliumNext/Trilium)

Fix landed in TriliumNext/Trilium commit 49fc7b67d9d4 — awaiting tagged release

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

TriliumNext/Trilium: unauthenticated share-search bypasses `shareCredentials` / `shareHiddenFromTree`, disclosing protected shared-note titles, paths and content · Advisory · TriliumNext/Trilium · GitHub

https://github.com/TriliumNext/Trilium/security/advisories/GHSA-6rxv-6w3q-7mv9

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 57× 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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 92 are merged into the row they repeat.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-77438?
CVE-2026-77438 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 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…
When was the CVE record for CVE-2026-77438 published?
The CVE record for CVE-2026-77438 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-77438 actively exploited?
CVE-2026-77438 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-77438?
CVE-2026-77438 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-77438?
The CVE record for CVE-2026-77438 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-77438

Explore →

Is Your Infrastructure Affected by CVE-2026-77438?

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

Book a Demo →Browse All CVEs