Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Command injection in Logseq desktop application enables remote code execution via shell metacharacter abuse in IPC-exposed command arguments. An attacker with JavaScript execution in the renderer process (through XSS or a malicious plugin) can bypass the command allowlist because arguments are concatenated and passed to child_process.spawn with shell:true, granting arbitrary OS command execution at the privileges of the Logseq process. No public exploit identified at time of analysis, but the issue was reported by CERT-PL and remains unpatched in versions beyond the tested v0.10.15.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Logseq gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Primary rating from Vendor (CERT-PL) · only source for this CVE.
CVSS VectorVendor: CERT-PL
Lifecycle Timeline
1DescriptionCVE.org
Logseq exposes an IPC handler that allows the renderer process to execute shell commands. While an allowlist restricts the command name (e.g. git, pandoc, grep), the argument string is concatenated with the command and passed to child_process.spawn with the shell: true option, allowing shell metacharacters in the arguments to bypass the allowlist. An attacker with JavaScript execution in the renderer (e.g. via XSS or a malicious plugin) can execute arbitrary shell commands with the privileges of the Logseq process, leading to remote code execution on the host. While only version v0.10.15 was tested and confirmed as vulnerable, status of other versions is unknown since this issue was not addressed by a patch.
Executive ViewAI
Logseq desktop application (versions v0.10.15 and later) contains a critical remote code execution vulnerability allowing attackers to execute arbitrary OS commands at the Logseq process privilege level. The vulnerability is reachable through JavaScript execution pathways including application plugins and content-based XSS, affecting any organization whose users install or rely on Logseq for document management or knowledge work. With no vendor patch available and full code execution capability, this represents immediate risk to sensitive data and system integrity for affected users.
Within 24 hours: Identify all Logseq installations (v0.10.15 and later) across the organization through asset inventory and endpoint tools. Within 7 days: Implement interim controls-restrict plugin installations to official Logseq repositories, disable untrusted plugin sources, enforce Content Security Policy if applicable, and apply application-level sandboxing where available; document exceptions and elevated risk. Within 30 days: Establish vendor monitoring for patch availability; evaluate alternative note-taking applications (Obsidian, Notion, Joplin with plugin restrictions) as potential replacements; maintain air-gapped or offline Logseq usage for sensitive documents until patch release.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) block execution of Logseq plugins except those from official sources; disable community plugin repositories entirely; (2) apply OS-level sandboxing (AppArmor, SELinux, or Windows Sandbox) to limit child process spawning and file system access; (3) monitor system audit logs for spawned child processes originating from Logseq process; (4) restrict Logseq instances from accessing sensitive network shares or environment variables; (5) maintain segregated or offline instances of Logseq for handling untrusted documents; (6) require administrator approval before plugin installation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-35435
GHSA-c3m5-8vv9-gg8p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB