CVE-2026-130679: SiYuan: stored XSS in Attribute View leads to desktop RCE
CRITICALSiYuan, a note-taking and knowledge management app, has a stored cross-site scripting flaw in its Attribute View rendering. The genAVValueHTML() function does not escape an image src value, so an attacker can store a URL containing a double quote and an onerror handler. In the Electron desktop app that script runs with Node.js access, which turns a note-level injection into OS command execution on the victim's machine (CVSS 9.0, critical, network vector, low complexity, low privileges, user interaction required). There is no KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so this is not an active-exploitation event. However, any shared or collaborative workspace where a low-privileged user can write Attribute View values is exposed to a trivial payload. The AI relevance is indirect, because this is a general knowledge tool that teams may use as a notes or knowledge layer for AI work. Upgrade all SiYuan desktop clients to 3.8.10 or later, and until then avoid opening notes or database rows from untrusted contributors.
What is the risk?
Critical by CVSS (9.0), but exploitation is gated on a low-privileged attacker being able to write Attribute View asset values and on a victim opening the bound note or row attribute panel. The payload is trivial, a malicious image URL with an onerror handler, and the scope change (S:C) means script in the renderer escapes into the host OS through Node.js integration. No KEV entry, no public exploit, no scanner template and no EPSS score are available as of publication, so likelihood is moderate and impact is high. Exposure is greatest in shared or synced workspaces and where notes are imported from external sources. The AI/ML link is tenuous: the product is classified as ml_ui, but the flaw is a classic web-UI injection with no model-specific component.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| siyuan | — | — | No patch |
Do you use siyuan? You're affected.
How severe is it?
What is the attack surface?
What should I do?
1 step1) Upgrade SiYuan to version 3.8.10 or later (the fix is in the commit referenced by GHSA-3qqh-fmrp-8vfq). 2) Until patched, do not open notes, databases or row attribute panels from untrusted or low-trust collaborators, and restrict who can edit Attribute View values in shared or synced workspaces. 3) Inventory SiYuan desktop installs across endpoints, for example through EDR or software inventory. 4) Audit existing Attribute View asset values for image URLs containing quotes, onerror, or other inline event handlers. 5) Detect: alert on SiYuan or Electron processes spawning shells or interpreters (cmd, powershell, bash, curl). 6) Rotate secrets, API keys and tokens on any workstation where a suspicious payload was found.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-130679?
SiYuan, a note-taking and knowledge management app, has a stored cross-site scripting flaw in its Attribute View rendering. The genAVValueHTML() function does not escape an image src value, so an attacker can store a URL containing a double quote and an onerror handler. In the Electron desktop app that script runs with Node.js access, which turns a note-level injection into OS command execution on the victim's machine (CVSS 9.0, critical, network vector, low complexity, low privileges, user interaction required). There is no KEV listing, no public exploit and no Nuclei template, and EPSS data is not yet available, so this is not an active-exploitation event. However, any shared or collaborative workspace where a low-privileged user can write Attribute View values is exposed to a trivial payload. The AI relevance is indirect, because this is a general knowledge tool that teams may use as a notes or knowledge layer for AI work. Upgrade all SiYuan desktop clients to 3.8.10 or later, and until then avoid opening notes or database rows from untrusted contributors.
Is CVE-2026-130679 actively exploited?
No confirmed active exploitation of CVE-2026-130679 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-130679?
1) Upgrade SiYuan to version 3.8.10 or later (the fix is in the commit referenced by GHSA-3qqh-fmrp-8vfq). 2) Until patched, do not open notes, databases or row attribute panels from untrusted or low-trust collaborators, and restrict who can edit Attribute View values in shared or synced workspaces. 3) Inventory SiYuan desktop installs across endpoints, for example through EDR or software inventory. 4) Audit existing Attribute View asset values for image URLs containing quotes, onerror, or other inline event handlers. 5) Detect: alert on SiYuan or Electron processes spawning shells or interpreters (cmd, powershell, bash, curl). 6) Rotate secrets, API keys and tokens on any workstation where a suspicious payload was found.
What systems are affected by CVE-2026-130679?
This vulnerability affects the following AI/ML architecture patterns: Developer workstations, Knowledge management and notes tools, Collaborative or synced workspaces.
What is the CVSS score for CVE-2026-130679?
CVE-2026-130679 has a CVSS v3.1 base score of 9.0 (CRITICAL).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0011User ExecutionAML.T0050Command and Scripting InterpreterCompliance Controls Affected
What are the technical details?
Original Advisory
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability in genAVValueHTML() that allows attackers who can store Attribute View asset values to inject script through an unescaped image src attribute. Attackers can store an image URL containing a double quote and onerror handler that executes OS commands via Node.js in the desktop app when victims open the bound note or row attribute panel.
Exploitation Scenario
An attacker with a low-privilege account in a shared SiYuan workspace, or a contributor to an imported or synced notebook, stores an Attribute View asset value whose image URL contains a double quote followed by an onerror handler. The handler calls Node.js child_process APIs. When a teammate, such as an ML engineer who keeps prompts, API keys and experiment notes in SiYuan, opens the bound note or the row attribute panel, the script runs in the desktop app. It executes OS commands, exfiltrates LLM provider keys, cloud credentials and SSH keys, and drops a reverse shell for pivoting into internal AI 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:HReferences
Timeline
Related Vulnerabilities
CVE-2024-291210.0BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Code ExecutionCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same attack type: Code ExecutionCVE-2025-512010.0smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code ExecutionCVE-2025-5952810.0Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code ExecutionGHSA-vvpj-8cmc-gx3910.0picklescan: security flaw enables exploitation
Same attack type: Code Execution