Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a small standalone PoC and explanatory material for CVE-2025-68621, a timing side-channel in TriliumNext/Trilium sync authentication. Structure: README.md documents the vulnerability, attack method, impact, and references; vulnerable.ts is a simplified TypeScript reproduction of the flawed loginSync logic using `expectedHash !== givenHash`; fix.ts shows the corrected constant-time comparison using `crypto.timingSafeEqual`; poc.py is the main exploit entry point. The Python exploit uses `requests.Session()` and `time.perf_counter()` to repeatedly send POST requests to `{TARGET_URL}/api/login/sync` with JSON fields `timestamp`, `syncVersion`, and attacker-controlled `hash`. It iterates over all 44 Base64 positions of the HMAC, tests each candidate character from a Base64 charset, collects 50 timing samples per candidate, uses the median response time to choose the most likely correct character, reconstructs the full HMAC, and then attempts authentication with the recovered value. This is an actual exploit rather than a detector: its end goal is unauthorized sync authentication/access. No external C2 or malware behavior is present; the only operational network target is the Trilium sync login endpoint.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.