External risk intelligence

SiYuan Electron Remote Code Execution via Malicious Note Sync.

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-39846

The vulnerability resides in a personal knowledge management desktop client. It requires a victim to sync a malicious note and open it within their local application environment. It is not an internet-facing service, edge gateway, or web-accessible endpoint.

Cross-site Scripting

B3log Siyuan

before 3.6.4

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the SiYuan personal knowledge management system that could allow a malicious note to trigger remote code execution on a user's desktop client. This occurs when a crafted note is synced and then opened, potentially executing attacker-controlled JavaScript with access to system APIs.

  • Malicious notes can execute code on your computer.
  • Data is not stored securely in note content.
  • Confirm if your organization uses this tool.

Attack Path

How an attacker could exploit the issue

An attacker can leverage this vulnerability by first importing a crafted malicious note into a shared SiYuan workspace. Once a victim synchronizes their workspace, the malicious note will be present on their device. When the victim opens this note, the stored cross-site scripting vulnerability is triggered, allowing the attacker to execute arbitrary code on the victim's machine due to the Electron client's configurations.

  • Requires access to a synced workspace.
  • Triggered by opening a crafted note.
  • Allows remote code execution.

Live Threat

Current exploitation, exposure, and threat context

A malicious note synced to another user could lead to remote code execution when the victim opens it, due to stored XSS vulnerabilities in the SiYuan Electron desktop client. This occurs when table caption content is unescaped into rendered HTML, allowing attacker-controlled JavaScript to execute with access to Node.js APIs because `nodeIntegration` is enabled and `contextIsolation` is disabled.

  • Data or system asset: User's local client.
  • How exposure could happen: Victim opens a crafted note.
  • Realistic consequence: Remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action for this vulnerability likely falls to application owners and potentially platform teams, depending on how SiYuan is deployed and managed. The immediate first step is to identify all instances of the affected SiYuan desktop client within the organization. Once identified, confirm if these instances are actively used for collaboration or syncing, as this dictates exposure, and then locate the accountable user or administrator for remediation planning.

  • Identify accountable SiYuan users or administrators.
  • Verify active syncing and note sharing.
  • Coordinate upgrade or remediation planning.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is SiYuan?

SiYuan is a personal knowledge management system designed for organizing notes and documents. It functions as a desktop application built on the Electron framework, which allows it to combine web technologies with local system access for features like data synchronization. Users typically use it to store and manage personal or collaborative information across different workspaces.

What does CVE-2026-39846 mean for my security?

This vulnerability involves a weakness known as Improper Neutralization of Input during Web Page Generation, or Stored XSS (CWE-79), combined with Improper Control of Generation of Code (CWE-94). Specifically, the software fails to sanitize table captions in notes. Because the application runs with elevated permissions, this allows malicious code hidden in a note to escape the application's sandbox and run commands directly on your computer.

How does an attacker trigger this vulnerability?

An attacker must gain access to a shared workspace to introduce a specially crafted note containing malicious content. The vulnerability is only triggered when a victim synchronizes their data and opens that specific note. It does not trigger simply by receiving the note or syncing the workspace in the background; the code execution requires the user to interact with the rendered note content within the desktop client.

Is my instance of SiYuan at risk?

According to Halo Surface Signal, this is considered very unlikely for typical infrastructure security because SiYuan is a desktop client rather than an internet-facing service or server. Risk is localized to users who actively participate in shared workspaces where they import content from untrusted sources. If you only use SiYuan locally for personal notes without syncing or sharing, the attack path is largely absent.

How do I secure my SiYuan installation?

The primary response is to update the SiYuan desktop client to version 3.6.4 or later, which contains the fix for the improper content handling. Organizations should identify users who have the application installed, verify if they are using synchronization features with shared workspaces, and prioritize upgrading those specific client instances to eliminate the vulnerable rendering behavior.

References