TCC access via enabled RunAsNode fuse
Published May 19, 2026 · Updated May 20, 2026
TCC prompt spoofing in Trilium Notes 0.102.1 and earlier allows local users to access protected macOS resources via deceptive prompts. The Electron desktop build leaves the RunAsNode fuse enabled, so its executable accepts Node.js code and inherits the app's identity and TCC grants. Exploitation requires local code execution and approval of a misleading permission prompt, after which attacker code can read protected files or capture the screen, camera, or microphone.
Summary
What happened
TCC prompt spoofing in Trilium Notes 0.102.1 and earlier allows local users to access protected macOS resources via deceptive prompts. The Electron desktop build leaves the RunAsNode fuse enabled, so its executable accepts Node.js code and inherits the app's identity and TCC grants. Exploitation requires local code execution and approval of a misleading permission prompt, after which attacker code can read protected files or capture the screen, camera, or microphone.
The record
- CVE
- CVE-2026-39309
- Published
- May 19, 2026
- Updated
- May 20, 2026
- Vendor
- Trilium Next
- Product
- Trilium Notes
- Classifications
- CWE-290, CWE-451, T1036
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 19, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.102.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory TCC prompt-spoofing reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo