# CVE-2026-9279: Shell command injection in Logseq

> Attackers with renderer access can execute arbitrary shell commands via IPC handler due to unsafe argument concatenation, leading to remote code execution.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-c3m5-8vv9-gg8p

## What is CVE-2026-9279?

CVE-2026-9279 is a high-severity command injection vulnerability in logseq, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-9279?


## How do I fix CVE-2026-9279?

No fix has been published for CVE-2026-9279 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9279 being exploited?

There is no known exploitation of CVE-2026-9279 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9279 and fix it if it is affected.

What it is: CVE-2026-9279 is a high-severity command injection vulnerability in logseq, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9279 in the wild and no public exploit code.

Affected product: logseq. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9279/ (Markdown: https://insights.sbomify.com/CVE-2026-9279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9279
- OSV: https://osv.dev/vulnerability/CVE-2026-9279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9279/
Summaries are generated and may contain mistakes; the official description above is the record.