{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39309 exists.","fix":"No fix has been published for CVE-2026-39309 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39309 is a medium-severity vulnerability in TriliumNext Trilium, published on 19 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-39309 and fix it if it is affected.\n\nWhat it is: CVE-2026-39309 is a medium-severity vulnerability in TriliumNext Trilium, published on 19 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39309 exists.\n\nAffected product: TriliumNext Trilium. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39309/ (Markdown: https://insights.sbomify.com/CVE-2026-39309/index.md)","id":"CVE-2026-39309","markdown":"https://insights.sbomify.com/CVE-2026-39309/index.md","name":"CVE-2026-39309","record":{"aliases":["GHSA-66pm-8hvq-2wwx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Trilium Notes","requires_auth":"none","summary":"Local attackers can bypass macOS TCC protections to access sensitive resources like camera and files by spoofing permission prompts via Electron's RunAsNode fuse.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-451","name":"User Interface (UI) Misrepresentation of Critical Information"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"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 Electron configuration is vulnerable to TCC Bypass via Prompt Spoofing, allowing local attackers to trigger misleading macOS permission prompts by running malicious code under the identity of the trusted app. The root cause is that the RunAsNode fuse allows launching the app in a special Node.js mode using -e to execute arbitrary system commands with Trilium Notes's permissions and identity. An attacker can leverage this through a subprocess to request any sensitive permissions, such as access to hardware (camera, microphone) and TCC-protected files, causing the TCC system prompt to appear as if the request came from Trilium rather than the attacker's code, because macOS treats the subprocess as part of the parent application. Exploitation allows access to TCC-protected resources like the screen, camera, microphone, and folders such as ~/Documents and ~/Downloads, undermining macOS's security model and UI integrity through social engineering. This issue has been fixed in version 0.102.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Trilium Notes: macOS TCC Bypass via Prompt Spoofing","id":"CVE-2026-39309","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Trilium Notes: Authentication Bypass in Clipper API for Electron (Desktop) Builds","id":"CVE-2026-39310"},"packages":[],"prev":{"headline":"PraisonAI recipe registry publish path traversal allows out-of-root file write","id":"CVE-2026-39308"},"products":["Trilium"],"published":"2026-05-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-20","vendors":["TriliumNext"]},"summary":"Local attackers can bypass macOS TCC protections to access sensitive resources like camera and files by spoofing permission prompts via Electron's RunAsNode fuse.","url":"https://insights.sbomify.com/CVE-2026-39309/"}