External risk intelligence

SiYuan Stored XSS via Unescaped Attribute Name

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-130681

SiYuan is a local-first personal knowledge management application typically run as a desktop client. The vulnerability is triggered by a user opening a specific panel within the application interface. It is not an internet-facing service, API, or network appliance, making external exploitation via the public internet highly unlikely in typical deployments.

Cross-site Scripting

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

This advisory details a vulnerability within SiYuan software that could allow unauthorized execution of commands. The issue stems from an incomplete fix for a previous vulnerability, where specific user-persistent data can lead to the execution of operating system commands when a desktop user opens a particular panel. While the vulnerability is rated critical, its exploitation requires specific user interaction and is unlikely in typical deployments.

  • Stored script injection enables OS command execution.
  • Exploitation requires user interaction, limiting broad risk.
  • Confirm relevance and assess exposure within deployments.

Attack Path

How an attacker could exploit the issue

An attacker with authenticated access could inject malicious code into a database attribute panel header, which would execute when a desktop user opens that panel. This stored cross-site scripting vulnerability can lead to the execution of operating system commands via Node.js.

  • Requires authenticated access.
  • Triggered by opening a specific panel.
  • Risk of OS command execution.

Live Threat

Current exploitation, exposure, and threat context

A stored cross-site scripting vulnerability could allow an attacker to execute OS commands through Node.js when a desktop user opens a specific panel, provided the attacker can first persist a malicious attribute view name.

  • System commands could be executed.
  • User interaction with a malicious panel triggers it.
  • Compromised desktop environment.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in SiYuan is likely to be owned by teams managing end-user application deployments, such as desktop support or IT administration, as it affects a local application. The first practical step is to identify all users running the affected software, confirm their exposure through usage patterns, and then coordinate remediation, potentially with vendor support.

  • Application owners should manage the issue.
  • Verify user deployment and usage.
  • Plan coordinated remediation actions.

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 local-first personal knowledge management application. It functions as a desktop-based tool that allows users to organize notes and information. Because it is designed to run locally on your computer rather than as a public web server, it prioritizes user control over private data, though this architecture means that security issues within the app impact the host desktop environment directly.

What is the vulnerability in CVE-2026-130681?

This vulnerability is a form of stored cross-site scripting (CWE-79). The software fails to properly sanitize input when handling Attribute View names. Because these names are saved directly into the database, an attacker can embed malicious scripts. When a user later views the affected panel, the application inadvertently runs that script, which can lead to the execution of unintended operating system commands via the underlying Node.js environment.

How is this SiYuan vulnerability triggered?

An attacker must first be able to persist a malicious name, such as through the setAttrViewName action. The flaw does not trigger automatically; it requires a legitimate user to open the specific database row attribute panel where the malicious name is stored. Simply having the malicious data present in the database is not enough to execute the code; the user interaction of opening the panel is the necessary final step.

Do I need to worry about this if I use SiYuan?

According to Halo Surface Signal, this risk is very unlikely to be exploited over the public internet. Because SiYuan is typically run as a local desktop client rather than a web-facing service, it lacks the standard network exposure that attackers usually target. You should prioritize this based on whether you share your SiYuan database with untrusted users who could inject malicious names.

When should I take action for CVE-2026-130681?

You should begin by identifying which users in your environment are running SiYuan versions earlier than 3.8.10. Once you have a list of users, assess their usage patterns—specifically if they collaborate on shared databases where external actors might inject data. Coordinate with these users to update the application, as updating to the latest version is the primary way to address this incomplete fix.

References