The National Vulnerability Database (NVD) has published three CRITICAL severity vulnerabilities in SiYuan, a popular open-source personal knowledge management (PKM) application built on Electron. Assigned CVE-2026-130680, CVE-2026-130679, and CVE-2026-130681, these flaws carry CVSS scores of up to 9.6 and are exploitable over the network via maliciously crafted documents.
The most severe vulnerability, CVE-2026-130680, is a stored cross-site scripting (XSS) flaw that allows attackers to execute arbitrary Node.js code within the context of the Electron desktop client. Given that SiYuan's desktop application runs with nodeIntegration enabled—a common but dangerous Electron configuration—successful exploitation results in full compromise of the underlying operating system with the privileges of the running user.
Security teams responsible for developer workstations, research environments, and knowledge-management infrastructure must treat this as a priority patching event. The network-exploitable nature of these flaws means that simply opening a shared .sy.zip document or rendering a malicious AttributeView can trigger code execution without additional user interaction beyond the initial document load.
Technical Analysis
Affected Products and Versions
| Product | Affected Versions | Fixed Version | Platform |
|---|---|---|---|
| SiYuan | 3.3.0 to 3.8.9 | 3.8.10 | Windows, macOS, Linux (Electron Desktop) |
| SiYuan | Prior to 3.8.10 | 3.8.10 | All supported desktop platforms |
Vulnerability Breakdown
CVE-2026-130680 (CVSS 9.6 - CRITICAL)
The vulnerability resides in the Gallery and Kanban AttributeView renderers within SiYuan. Specifically, checkbox column names are not properly escaped or sanitized before being rendered in the DOM. An attacker can inject malicious HTML/JavaScript payloads into these column names, which are then stored within the SiYuan document (.sy.zip format).
When a victim opens the crafted document or switches to the affected Gallery/Kanban view, the payload executes in the renderer process. Because SiYuan's Electron implementation enables nodeIntegration, the JavaScript context has direct access to Node.js APIs—including child_process, fs, and net—allowing arbitrary command execution, file system access, and network operations.
CVE-2026-130679 (CVSS 9.0 - CRITICAL)
A second stored XSS vulnerability exists in the genAVValueHTML() function. This function is responsible for generating HTML representations of AttributeView values. Insufficient output encoding allows attackers to inject script content that executes when the AttributeView is rendered. Like CVE-2026-130680, this leads to Node.js code execution in the Electron context.
CVE-2026-130681 (CVSS 9.0 - CRITICAL)
This vulnerability represents an incomplete fix for a previous CVE (exact predecessor not disclosed in initial NVD data). The patch for the earlier vulnerability failed to address all code paths, leaving residual injection vectors in the AttributeView rendering pipeline. This is a common pattern in web-based desktop applications where multiple rendering functions handle similar data types without centralized sanitization.
Attack Chain and Exploitation Requirements
- Delivery: Attacker crafts a
.sy.zipfile containing a malicious SiYuan document with poisoned checkbox column names in a Gallery or Kanban AttributeView. - Social Engineering: The document is shared via email, chat, cloud storage, or public repository—framed as a legitimate knowledge base, meeting notes, or project documentation.
- Trigger: Victim opens the document in the SiYuan Electron desktop client (vulnerable version). The AttributeView renderer processes the unescaped column names.
- Execution: Malicious JavaScript executes with Node.js privileges. Attacker gains the ability to spawn processes, read/write files, establish persistence, and pivot to internal networks.
- Post-Exploitation: Given the Electron architecture, attackers can execute operating system commands, access browser-stored credentials, and potentially deploy additional payloads such as ransomware or espionage tools.
Exploitation Status
As of the NVD publication date (within the last 72 hours), these vulnerabilities are newly disclosed with no confirmed in-the-wild exploitation reported in public sources. However, the network-exploitable nature, high CVSS scores, and the fact that SiYuan documents are designed for sharing make weaponization highly likely in the near term. Proof-of-concept (PoC) code is expected to emerge rapidly given the straightforward nature of stored XSS-to-RCE chains in Electron applications.
These CVEs are not yet listed in the CISA Known Exploited Vulnerabilities (KEV) catalog as of this writing, but organizations should treat them with the same urgency as KEV entries due to the critical severity and ease of exploitation.
Detection & Response
Sigma Detection Rules
The following Sigma rules detect post-exploitation behaviors associated with successful exploitation of these vulnerabilities—specifically, the SiYuan Electron process spawning unexpected child processes or creating persistence mechanisms.
---
title: SiYuan Electron Process Spawning Shell or Scripting Engine
id: 7f3a9b2e-4c5d-4e8f-9a1b-3c6d8e2f4a5b
status: experimental
description: Detects SiYuan Electron process spawning command shells, PowerShell, or scripting engines, which may indicate successful exploitation of CVE-2026-130680 or related stored XSS vulnerabilities.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-130680
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/04/08
tags:
- attack.execution
- attack.t1059
- attack.t1059.003
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\SiYuan.exe'
- '\siyuan.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
- '\regsvr32.exe'
condition: selection_parent and selection_child
falsepositives:
- Legitimate SiYuan plugin execution (rare)
- User-initiated command execution from within SiYuan (uncommon)
level: high
---
title: SiYuan Process Establishing Network Connection to External IP
id: 8e4b1c9d-5f6a-4b7c-8d9e-2f3a4b5c6d7e
status: experimental
description: Detects SiYuan.exe establishing outbound network connections to non-RFC1918 addresses, which may indicate command-and-control communication following XSS exploitation.
references:
- https://nvd.nist.gov/vuln/detail/CVE-2026-130680
- https://attack.mitre.org/techniques/T1071/
author: Security Arsenal
date: 2026/04/08
tags:
- attack.command_and_control
- attack.t1071
logsource:
category: network_connection
product: windows
detection:
selection:
Image|endswith:
- '\SiYuan.exe'
- '\siyuan.exe'
filter_local:
DestinationIp|startswith:
- '10.'
- '172.16.'
- '172.17.'
- '172.18.'
- '172.19.'
- '172.20.'
- '172.21.'
- '172.22.'
- '172.23.'
- '172.24.'
- '172.25.'
- '172.26.'
- '172.27.'
- '172.28.'
- '172.29.'
- '172.30.'
- '172.31.'
- '192.168.'
- '127.'
condition: selection and not filter_local
falsepositives:
- SiYuan synchronization to cloud services (if configured)
- Update checks to SiYuan servers
level: medium
KQL Hunt Queries (Microsoft Sentinel / Defender)
Use these queries to hunt for exploitation attempts and post-exploitation behaviors across your environment. These assume ingestion of Windows Security Events (4688) and/or Microsoft Defender for Endpoint data.
Hunt 1: SiYuan Process Spawning Suspicious Child Processes
DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where InitiatingProcessFileName =~ "SiYuan.exe" or InitiatingProcessFileName =~ "siyuan.exe"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "wscript.exe", "cscript.exe", "mshta.exe", "rundll32.exe", "regsvr32.exe", "certutil.exe", "bitsadmin.exe")
| project TimeGenerated, DeviceName, AccountName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, SHA256, InitiatingProcessSHA256
| order by TimeGenerated desc
Hunt 2: SiYuan Network Connections to External IPs (Defender for Endpoint)
DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where InitiatingProcessFileName =~ "SiYuan.exe" or InitiatingProcessFileName =~ "siyuan.exe"
| where RemoteIPType == "Public"
| where RemoteUrl !contains "siyuan" and RemoteUrl !contains "github" and RemoteUrl !contains "microsoft"
| summarize Connections=count(), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by DeviceName, RemoteIP, RemoteUrl, InitiatingProcessCommandLine
| order by Connections desc
Hunt 3: Process Creation Events from SiYuan Parent (SecurityEvent)
SecurityEvent
| where TimeGenerated > ago(7d)
| where EventID == 4688
| where ParentProcessName endswith "SiYuan.exe" or ParentProcessName endswith "siyuan.exe"
| where NewProcessName endswith "cmd.exe" or NewProcessName endswith "powershell.exe" or NewProcessName endswith "wscript.exe" or NewProcessName endswith "cscript.exe"
| project TimeGenerated, Computer, Account, NewProcessName, CommandLine, ParentProcessName
| order by TimeGenerated desc
Velociraptor VQL Hunt
Deploy this VQL artifact across endpoints to identify suspicious process execution trees originating from SiYuan, which may indicate active or historical exploitation.
-- Hunt for SiYuan.exe spawning suspicious child processes (potential CVE-2026-130680 exploitation)
SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime,
dict(Pid=Ppid, Name=parent_name) as ParentProcess
FROM pslist()
WHERE Name =~ '(?i)siyuan'
OR Ppid IN (
SELECT Pid
FROM pslist()
WHERE Name =~ '(?i)siyuan'
)
AND Name =~ '(?i)(cmd|powershell|pwsh|wscript|cscript|mshta|rundll32|regsvr32|certutil|bitsadmin)'
Verification and Remediation Script
Use the following PowerShell script to identify vulnerable SiYuan installations and enforce upgrade to version 3.8.10 or later. Run this on endpoints via your preferred deployment mechanism (Intune, SCCM, GPO, or manual execution).
# SiYuan Vulnerability Remediation Script
# Checks for vulnerable versions and provides upgrade guidance
$SiYuanPaths = @(
"$env:LOCALAPPDATA\Programs\SiYuan\SiYuan.exe",
"$env:ProgramFiles\SiYuan\SiYuan.exe",
"$env:ProgramFiles (x86)\SiYuan\SiYuan.exe"
)
$VulnerableFound = $false
foreach ($path in $SiYuanPaths) {
if (Test-Path $path) {
$VersionInfo = (Get-Item $path).VersionInfo.ProductVersion
Write-Host "[+] Found SiYuan at: $path" -ForegroundColor Cyan
Write-Host "[+] Version: $VersionInfo" -ForegroundColor Cyan
# Parse version for comparison
if ($VersionInfo -match '^(\d+)\.(\d+)\.(\d+)') {
$Major = [int]$Matches[1]
$Minor = [int]$Matches[2]
$Patch = [int]$Matches[3]
# Vulnerable: 3.3.0 to 3.8.9 (fixed in 3.8.10)
if ($Major -eq 3) {
if (($Minor -gt 3) -and ($Minor -lt 8)) {
$VulnerableFound = $true
Write-Host "[!] VULNERABLE: Version $VersionInfo is affected by CVE-2026-130680/130679/130681" -ForegroundColor Red
}
elseif (($Minor -eq 8) -and ($Patch -lt 10)) {
$VulnerableFound = $true
Write-Host "[!] VULNERABLE: Version $VersionInfo is affected by CVE-2026-130680/130679/130681" -ForegroundColor Red
}
elseif ($Minor -eq 3) {
$VulnerableFound = $true
Write-Host "[!] VULNERABLE: Version $VersionInfo is affected by CVE-2026-130680/130679/130681" -ForegroundColor Red
}
else {
Write-Host "[OK] Version $VersionInfo appears to be patched or not in affected range" -ForegroundColor Green
}
}
}
# Check for suspicious child processes (basic IOC check)
$SiYuanProcs = Get-Process | Where-Object { $_.Path -like "*SiYuan*" }
foreach ($proc in $SiYuanProcs) {
$Children = Get-CimInstance Win32_Process | Where-Object { $_.ParentProcessId -eq $proc.Id }
foreach ($child in $Children) {
if ($child.Name -match '^(cmd|powershell|wscript|cscript|mshta|rundll32)') {
Write-Host "[!] ALERT: SiYuan spawned suspicious child process: $($child.Name) (PID: $($child.ProcessId))" -ForegroundColor Red
Write-Host " Command Line: $($child.CommandLine)" -ForegroundColor Red
$VulnerableFound = $true
}
}
}
}
}
if ($VulnerableFound) {
Write-Host "`n[CRITICAL] Immediate action required:" -ForegroundColor Red
Write-Host "1. Disconnect affected systems from network if active exploitation suspected" -ForegroundColor Yellow
Write-Host "2. Download SiYuan 3.8.10 or later from: https://github.com/siyuan-note/siyuan/releases" -ForegroundColor Yellow
Write-Host "3. Update all SiYuan installations immediately" -ForegroundColor Yellow
Write-Host "4. Review recent .sy.zip file access and opening activities" -ForegroundColor Yellow
exit 1
} else {
Write-Host "`n[INFO] No vulnerable SiYuan installations detected or no suspicious activity found." -ForegroundColor Green
exit 0
}
Remediation
Immediate Actions (Within 24 Hours)
-
Patch Immediately: Upgrade all SiYuan desktop installations to version 3.8.10 or later. Download from the official repository: https://github.com/siyuan-note/siyuan/releases
-
Block Untrusted Documents: Until patching is complete, instruct users not to open
.sy.zipfiles from untrusted or unknown sources. Implement email gateway rules to quarantine SiYuan document attachments if feasible. -
Disable SiYuan Cloud Sync (Temporary): If using SiYuan's cloud synchronization, temporarily disable it to prevent malicious documents from propagating across devices.
Configuration Hardening
-
Disable nodeIntegration (If Possible): While SiYuan requires this for functionality, verify if the application offers any configuration to restrict Node.js integration. Monitor the SiYuan GitHub repository for security-focused configuration options.
-
Application Whitelisting: Consider implementing application whitelisting (Windows Defender Application Control, AppLocker) to restrict which executables can launch from within SiYuan's process space.
-
Electron Security Best Practices: For organizations developing or deploying similar Electron-based applications, ensure
nodeIntegrationis disabled unless absolutely necessary, and implement strict Content Security Policy (CSP) headers.
Verification
After patching, verify the installation by checking the version number in SiYuan's "About" dialog or by examining the file properties of SiYuan.exe. The version should read 3.8.10 or higher.
Long-term Recommendations
- Document Handling Policies: Establish policies requiring sandboxed detonation or isolated viewing of PKM documents from external sources.
- User Awareness: Educate users about the risks of opening knowledge-base documents from untrusted sources, particularly those requesting to open AttributeViews or specific database views.
- Network Segmentation: Consider restricting SiYuan's network access via host-based firewalls if cloud synchronization is not required, limiting potential C2 communication channels.
Vendor References
- NVD Entry: https://nvd.nist.gov/vuln/detail/CVE-2026-130680
- SiYuan Releases: https://github.com/siyuan-note/siyuan/releases
- SiYuan GitHub Security Advisories: Monitor https://github.com/siyuan-note/siyuan/security/advisories for official patches and mitigation guidance.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.