Home

Description

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.

PUBLISHED Reserved 2026-05-22 | Published 2026-06-09 | Updated 2026-06-09 | Assigner CERT-PL




HIGH: 8.7CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Problem types

CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Product status

Default status
unknown

Any version
affected

Credits

Bartłomiej Dmitruk (striga.ai) finder

References

cert.pl/en/posts/2026/06/CVE-2026-9279/ third-party-advisory

logseq.com/ product

cve.org (CVE-2026-9279)

nvd.nist.gov (CVE-2026-9279)

Download JSON