CVE-2026-9279: Shell command injection in Logseq
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 childprocess.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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-9279?
CVE-2026-9279 has a high severity rating of 8.7 according to the CVSS scoring system.
How do I fix CVE-2026-9279?
To remediate CVE-2026-9279, ensure that you validate and sanitize inputs to prevent command injection and upgrade to the latest version of Logseq.
What type of vulnerability is CVE-2026-9279?
CVE-2026-9279 is classified as an OS Command Injection vulnerability, which allows execution of arbitrary shell commands.
Which software is affected by CVE-2026-9279?
CVE-2026-9279 affects Logseq, specifically its IPC handler functionality.
When was CVE-2026-9279 published?
CVE-2026-9279 was published on June 9, 2026.