CVE-2026-130681: SiYuan: stored XSS in Attribute View leads to desktop RCE

CRITICAL
Published November 18, 2026
CISO Take

SiYuan before 3.8.10 has a stored cross-site scripting flaw in the Attribute View name, and it is an incomplete fix for CVE-2026-44670. Because the SiYuan desktop client runs on Electron with Node.js access, injected script can run operating system commands on the user's machine, which is why the score is critical (CVSS 9.0, scope changed). The attacker needs only low privileges and a victim who opens the database row attribute panel. There is no CISA KEV listing, no public exploit and no Nuclei template yet, and no EPSS data is available, so active exploitation is unconfirmed. Because this is a repeat bypass of an earlier fix, expect researchers to move quickly on weaponization. Upgrade SiYuan to 3.8.10 or later, and until you can, avoid opening workspaces or shared notebooks from untrusted sources.

Sources:NVDGitHub AdvisoryATLAS

What is the risk?

High. The CVSS 9.0 vector (AV:N/AC:L/PR:L/UI:R/S:C) means the flaw is exploitable remotely with low complexity, but it needs low privileges and one user action. The changed scope reflects a jump from the web renderer to the host OS through Node.js integration. Exploitation signals are limited: no KEV entry, no public exploit, no scanner template and no EPSS score. This is an incomplete fix for CVE-2026-44670, so the bug class has already been shown to be reachable and patch coverage was incomplete. Exposure is greatest in collaborative or synced workspaces where other users can edit Attribute View names. Package risk data (0/100, no dependents or scorecard) is missing, so blast radius is unknown.

How does the attack unfold?

Initial Access
An attacker with low privileges persists a malicious Attribute View name via the setAttrViewName action.
AML.T0049
User Trigger
A desktop user opens the database row attribute panel, and renderAVAttribute() renders the name unescaped.
AML.T0011
Execution
The injected onerror handler runs OS commands through Node.js in the Electron client.
AML.T0050
Impact
The attacker gains code execution on the host and can steal credentials, notes and AI project secrets.

What systems are affected?

PackageEcosystemVulnerable RangePatched
siyuan——No patch

Do you use siyuan? You're affected.

How severe is it?

CVSS 3.1
9.0 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRLow
UIRequired
SChanged
CHigh
IHigh
AHigh

What should I do?

1 step
  1. 1) Upgrade SiYuan to 3.8.10 or later (see the vendor advisory GHSA-7gj8-xf7w-hfjf and the patch commit d3af9d5). 2) Until patched, do not open untrusted or shared workspaces and restrict write access to shared notebooks. 3) Audit existing Attribute View names for HTML or script content, such as onerror, <img or <script strings, in workspace data. 4) Monitor endpoints for the SiYuan process spawning shells or unexpected child processes (cmd.exe, powershell, sh, bash, curl). 5) Rotate any credentials or API keys stored in SiYuan notes if suspicious activity is found. 6) Restrict network exposure of self-hosted SiYuan instances and require authentication.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.10.3-Suppliers
NIST AI RMF
MANAGE 2.3-Responses to previously unknown risks and risk treatment
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-130681?

SiYuan before 3.8.10 has a stored cross-site scripting flaw in the Attribute View name, and it is an incomplete fix for CVE-2026-44670. Because the SiYuan desktop client runs on Electron with Node.js access, injected script can run operating system commands on the user's machine, which is why the score is critical (CVSS 9.0, scope changed). The attacker needs only low privileges and a victim who opens the database row attribute panel. There is no CISA KEV listing, no public exploit and no Nuclei template yet, and no EPSS data is available, so active exploitation is unconfirmed. Because this is a repeat bypass of an earlier fix, expect researchers to move quickly on weaponization. Upgrade SiYuan to 3.8.10 or later, and until you can, avoid opening workspaces or shared notebooks from untrusted sources.

Is CVE-2026-130681 actively exploited?

No confirmed active exploitation of CVE-2026-130681 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-130681?

1) Upgrade SiYuan to 3.8.10 or later (see the vendor advisory GHSA-7gj8-xf7w-hfjf and the patch commit d3af9d5). 2) Until patched, do not open untrusted or shared workspaces and restrict write access to shared notebooks. 3) Audit existing Attribute View names for HTML or script content, such as onerror, <img or <script strings, in workspace data. 4) Monitor endpoints for the SiYuan process spawning shells or unexpected child processes (cmd.exe, powershell, sh, bash, curl). 5) Rotate any credentials or API keys stored in SiYuan notes if suspicious activity is found. 6) Restrict network exposure of self-hosted SiYuan instances and require authentication.

What systems are affected by CVE-2026-130681?

This vulnerability affects the following AI/ML architecture patterns: Desktop knowledge-management clients (Electron), Shared or synced note workspaces, Developer workstations in ML teams.

What is the CVSS score for CVE-2026-130681?

CVE-2026-130681 has a CVSS v3.1 base score of 9.0 (CRITICAL).

What is the AI security impact?

Affected AI Architectures

Desktop knowledge-management clients (Electron)Shared or synced note workspacesDeveloper workstations in ML teams

MITRE ATLAS Techniques

AML.T0011User Execution
AML.T0050Command and Scripting Interpreter

Compliance Controls Affected

ISO 42001: A.10.3
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel.

Exploitation Scenario

An attacker with a low-privilege account on a shared or synced SiYuan workspace calls the setAttrViewName action to set an Attribute View name that contains an HTML payload, such as an img tag with an onerror handler. The payload is stored. When a colleague on the desktop client opens the database row attribute panel, renderAVAttribute() inserts the name unescaped and the handler runs. The script uses Node.js child_process to launch OS commands, for example to download a second-stage payload or copy SSH keys, cloud credentials and model registry tokens from the victim's machine. The attacker then uses these to reach internal ML repositories and training infrastructure.

Weaknesses (CWE)

CWE-79 — Improper Neutralization of Input During Web Page Generation: The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

  • [Architecture and Design] Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Examples of libraries and frameworks that make it easier to generate properly encoded output include Microsoft's Anti-XSS library, the OWASP ESAPI Encoding module, and Apache Wicket.
  • [Implementation, Architecture and Design] Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies. For any data that will be output to another web page, especially any data that was received from external inputs, use the appropriate encoding on all non-alphanumeric characters. Parts of the same output document may require different encodings, which will vary depending on whether the output is in the: etc. Note that HTML Entity Encoding is only appropriate for the HTML body. Consult the XSS Prevention Cheat Sheet [REF-724] for more details on the types of encoding and escaping that are needed. HTML body Element attributes (such as src="XYZ") URIs JavaScript sections Casca

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Timeline

Published
November 18, 2026
Last Modified
November 18, 2026
First Seen
November 18, 2026

Related Vulnerabilities