High exploit reference

CVE-2025-68621 — Trilium Notes has a Timing Attack Vulnerability in /api/login/sync

Trilium Notes is an open-source, cross-platform hierarchical note taking application with focus on building large personal knowledge bases. Prior to 0.101.0, a critical timing attack vulnerability in Trilium's sync authentication endpoint allows unauthenticated remote attackers to recover HMAC authentication hashes byte-by-byte through statistical timing analysis. This enables complete authentication bypass without password knowledge, granting full read/write access to victim's knowledge base. This vulnerability is fixed in 0.101.0.

Published Feb 6, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.6% (30-day exploitation probability)+7
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.57%

ahead of 46% of scored CVEs · Oct 14, 2026

Affects

TriliumNext

Trilium

CVSS base

7.4

High · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

Documented patch — github.com (NIST National Vulnerability Database)
Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (TriliumNext Trilium, Triliumnotes Trilium).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
Apply the fixed version or the patch documented under Remediation.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
TriliumNext	Trilium	version < 0.101.0	Vulnerable	CVE Program (cve.org) e CISA ADP
Triliumnotes	Trilium	< 0.101.0	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.4	CVSS 3.1	High	2.2	5.2	security-advisories@github.com via NIST National Vulnerability Database
7.4	CVSS 3.1	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-208

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.57%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · triliumnext/trilium
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
Fix documented
Oct 13, 2026 · NIST National Vulnerability Database
CVSS changed · 7.4
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Feb 6, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/TriliumNext/Trilium/pull/8129
Issue Tracking, Patch, x_refsource_MISC, NIST National Vulnerability Database
github.com/TriliumNext/Trilium/security/advisories/GHSA-hxf6-58cx-qq3x
Exploit, Mitigation, Patch, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database

Elsewhere on this site

TriliumNext
every CVE for this vendor

CWE-208
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-77438 Trilium unauthenticated share-search discloses password-protected and hidden shared notes Aug 27, 2026
Medium CVE-2026-53579 Trilium: Note Import to RCE via Book Note Aug 27, 2026
High CVE-2026-53580 Trilium arbitrary file read and denial of service via file:// URLs in the automatic image-download feature Aug 27, 2026
Medium CVE-2026-53578 Trilium: Note Import to RCE via Mind Elixir dangerouslySetInnerHtml Aug 27, 2026
Medium CVE-2026-48996 Trilium: Malicious import with GeoMap marker title XSS leads to RCE on the desktop client Aug 27, 2026
High CVE-2026-47727 Trilium: RCE via `shareTemplate` relation missing `isDangerous` flag — Safe import bypass leading to EJS SSTI (Incomplete Fix of CVE-2026-45668) Aug 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-68621 is "Trilium Notes has a Timing Attack Vulnerability in /api/login/sync", rated High. It affects Trilium (TriliumNext); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.4 describes technical severity. EPSS 0.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.