Skip to main content

Logseq EUVDEUVD-2026-35435

| CVE-2026-9279 HIGH
OS Command Injection (CWE-78)
2026-06-09 CERT-PL GHSA-c3m5-8vv9-gg8p
8.7
CVSS 4.0 · Vendor: CERT-PL
View

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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

logseq 0 ≤0.10.15

Affected Packages

euvd logseq no fix

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

Vendor (CERT-PL) PRIMARY 8.7 HIGH
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

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
Jun 09, 2026 - 14:22 NVD
8.7 (HIGH)

DescriptionCVE.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

Why It Matters

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.

Recommended Action

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.

Business Impact: Severe
Compensating Controls

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

EPSS Score
0.1%
Top 75% exploitable
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

Related Vulnerabilities in Logseq Electron IPC and XSS Vulnerabilities

View all 4

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy