CVE-2026-39310

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.6 under NVD CVSS v3. 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 NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-31156 (ENISA EUVD)Source: ENISA EUVD

8.6EG
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: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Trilium Notes is a cross-platform, hierarchical note taking application focused on building large personal knowledge bases. In versions 0.102.1 and prior, the Clipper API in Trilium Desktop (v0.101.3) allows full authentication bypass when running in an Electron environment. When Trilium detects an Electron environment, it explicitly disables authentication middleware for the Clipper API, exposing endpoints such as /api/clipper/notes to the network with no password, API token, or CSRF protection. An attacker on a shared network (for example, a corporate LAN or public Wi-Fi) can scan for open high-range ports using a tool like nmap, since Trilium often binds to ports such as 37840. Once a candidate port is found, an unauthenticated request to the Clipper handshake endpoint, which also bypasses authentication, confirms a Trilium instance by returning the application name and protocol version. This facilitates unauthorized data access, phishing, and local system compromise. The issue has been fixed in version 0.102.2.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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: A fix is available. 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

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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

A fix is available. 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.

The score's inputs: 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

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 3, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Authentication Bypass in Clipper API for Electron (Desktop) Builds · Advisory · TriliumNext/Trilium · GitHub

https://github.com/TriliumNext/Trilium/security/advisories/GHSA-jcvx-vc83-cppw
GitHub release Patch Available

v0.102.2

Patch available: TriliumNext/Trilium v0.102.2

https://github.com/TriliumNext/Trilium/releases/tag/v0.102.2

Weakness Classification(2)

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

Data Freshness Timeline

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

Showing the most recent 99 of 213 refreshes on record for this CVE.

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-39310?
CVE-2026-39310 is a high-severity vulnerability; its CVE record was published on May 20, 2026. Trilium Notes is a cross-platform, hierarchical note taking application focused on building large personal knowledge bases. In versions 0.102.1 and prior, the Clipper API in Trilium Desktop (v0.101.3) allows full authentication bypass when running in an Electron environment. When Trilium detects an…
When was the CVE record for CVE-2026-39310 published?
The CVE record for CVE-2026-39310 was published on May 20, 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 July 23, 2026; the record at its source may have been updated since.
Is CVE-2026-39310 actively exploited?
CVE-2026-39310 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-39310?
CVE-2026-39310 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-39310?
A fix for CVE-2026-39310 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-39310

Explore →

Is Your Infrastructure Affected by CVE-2026-39310?

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