VYPR
High severityNVD Advisory· Published Jun 9, 2026· Updated Jun 9, 2026

CVE-2026-9279

CVE-2026-9279

Description

Logseq's IPC handler allows command injection via shell metacharacters in arguments, enabling RCE.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Logseq's IPC handler allows command injection via shell metacharacters in arguments, enabling RCE.

Vulnerability

Logseq versions up to and including v0.10.15 are vulnerable to OS command injection. An IPC handler intended to execute specific commands like git, pandoc, or grep concatenates user-supplied arguments directly with the command and passes them to child_process.spawn with shell: true. This allows shell metacharacters within the arguments to bypass the command allowlist [1].

Exploitation

An attacker requires JavaScript execution within the Logseq renderer process, which can be achieved through cross-site scripting (XSS) vulnerabilities or a malicious Logseq plugin. Once JavaScript execution is achieved, the attacker can craft arguments containing shell metacharacters to inject arbitrary commands. These commands are then executed with the privileges of the Logseq application process [1].

Impact

Successful exploitation allows an attacker to execute arbitrary shell commands on the host system with the same privileges as the Logseq process. This can lead to remote code execution (RCE) and a full compromise of the affected machine, depending on the privileges Logseq is running with [1].

Mitigation

No patch has been released to address this vulnerability, and the status of versions beyond v0.10.15 is unknown. Therefore, no fixed version is available. Users are advised to be cautious with plugins and external inputs that could lead to JavaScript execution within Logseq [1].

AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.