On this page (7 sections)
A critical stored cross-site scripting (XSS) flaw, tracked as CVE-2026-130678, affects SiYuan versions before 3.8.10. According to the GitHub Advisory Database entry, a malicious Attribute View column name is rendered without escaping, and on the desktop app the resulting script runs with Node.js privileges, which means code execution on the user's machine.
Anyone who runs SiYuan, especially on a desktop, and anyone who imports shared notebooks or syncs data from other people should check their version now. The advisory is currently the only detailed source and is marked as unreviewed, so some details below are flagged as unconfirmed.
What happened
The flaw was published on Nov 18, 2026 through the National Vulnerability Database and mirrored in the GitHub Advisory Database. SiYuan is a note-taking and knowledge management application. Its Attribute View feature presents database-style tables, and each table has columns with user-defined names.
The description says those column names are written into the page without proper escaping in the file col.ts. If a name contains HTML, it is interpreted as markup instead of plain text. Because the injected content is stored, it fires later when a user performs a normal action on the column.
Technical details
This is a classic stored XSS (CWE-79), but the setting makes it more serious than the same bug in an ordinary website. The advisory states that when a victim adds or duplicates the affected column, the code path uses insertAdjacentHTML, which runs JavaScript with Node.js privileges. In a desktop app built on a web runtime, that level of access can reach the operating system, which is why the advisory describes the outcome as desktop code execution.
According to the advisory, an attacker can get the malicious column name into a workspace in three ways:
- Through the addAttributeViewKey operation.
- Through importing a crafted .sy.zip file.
- Through sync, where content from another source arrives in the victim's workspace.
The CVSS v4 metrics in the advisory list a network attack vector, low attack complexity, low privileges required and passive user interaction, with high impact on confidentiality, integrity and availability for both the vulnerable and subsequent systems. The research does not include a proof of concept or exploitation details, and this article does not add any.
Who is affected
Exposure depends on how you use SiYuan:
- Desktop users on a version older than 3.8.10 carry the highest risk, since the described impact is code execution with Node.js privileges.
- Teams that share workspaces or use sync are exposed to content that someone else created.
- People who import .sy.zip files from third parties, forums or shared templates can pull in a malicious column name without noticing.
- Self-hosted deployments reachable by several users also deserve a version check, although the research focuses on the desktop impact and does not describe server-side effects.
The research does not say whether any attacks have happened, and it names no victims or threat actors.
How to check your exposure
- Open SiYuan and find the version number in the application's About or settings area, then compare it with 3.8.10.
- For self-hosted or container deployments, check the image tag or release you deployed and note every machine that runs a desktop client against the same workspace.
- List which workspaces receive synced content or imported .sy.zip files from other people, since those are the entry points named in the advisory.
- Review Attribute View tables in shared workspaces for column names that contain HTML tags or look unusual. Do not add or duplicate such a column to test it.
What to do now
- Update SiYuan to 3.8.10 or later on every desktop and server installation, using the project's official releases.
- Until everyone has updated, avoid adding or duplicating Attribute View columns in workspaces that contain content from other people.
- Do not import .sy.zip files from sources you do not trust, and pause sync with untrusted accounts or workspaces.
- Review shared Attribute View column names for HTML-like content and remove anything suspicious through a patched client.
- If a suspicious column was added or duplicated on an unpatched desktop, treat that machine as potentially compromised: change passwords and tokens stored on it, check for unfamiliar processes and startup items, and rotate any API keys kept in notes.
- Back up your workspace before updating, and confirm the fix status in the project's own advisory because the public database entry lists patched versions as Unknown.
Detection and monitoring
There are no published indicators of compromise in the research, so detection is mostly about hygiene. Keep an inventory of SiYuan versions across your team, and watch the project's release notes and security advisories for follow-up details, including a confirmed fixed version and any additional affected components.
If you expose a self-hosted instance to the internet, a read-only check of the public side helps you spot unexpected changes. Webforta Monitor can watch certificates, DNS and header changes, and the free security headers checker shows which browser protections your instance sends. Neither tells you whether a desktop client is vulnerable, so version checks remain the main control.
Timeline
| Date | Event |
|---|---|
| Nov 18, 2026 | CVE-2026-130678 published by NVD and added to the GitHub Advisory Database |
| Nov 18, 2026 | GitHub entry last updated; still marked Unreviewed |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
