Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-ff66-236v-p4fg

HIGH

GHSA-ff66-236v-p4fg is a high-severity (CVSS 8.6) Cross-site Scripting (XSS) vulnerability in github.com/siyuan-note/siyuan/kernel. O3 Security confirms whether GHSA-ff66-236v-p4fg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SiYuan Desktop: Stored XSS in imported .sy.zip content leads to arbitrary command execution

Also known asCVE-2026-34585GO-2026-5357
Published
Apr 1, 2026
Updated
Jun 25, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
🐹github.com/siyuan-note/siyuan/kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A vulnerability allows crafted block attribute values to bypass server-side attribute escaping when an HTML entity is mixed with raw special characters. An attacker can embed a malicious IAL value inside a .sy document, package it as a .sy.zip, and have the victim import it through the normal Import -> SiYuan .sy.zip workflow. Once the note is opened, the malicious attribute breaks out of its original HTML context and injects an event handler, resulting in stored XSS. In the Electron desktop client, this XSS reaches remote code execution because injected JavaScript runs with access to Node/Electron APIs.

Details

The issue is caused by a logic regression in escapeNodeAttributeValues in kernel/filesys/tree.go. Previously, the escaping logic converted node.KramdownIAL with parse.IAL2Map(...) before deciding whether a value needed escaping. That conversion unescaped existing entities first, so mixed values such as:

&" onmouseenter="alert('IAL-XSS')

were still recognized as unsafe and escaped correctly. The logic changed to inspect raw KramdownIAL values directly. The new needsEscapeForValue implementation returns false as soon as it sees any known entity such as &, ", <, or >. This means a value containing both an entity and an unescaped raw quote bypasses escaping entirely.

That bypass becomes exploitable because the renderer later inserts block IAL values directly into HTML attributes. A payload like:

&" onmouseenter="require('child_process').exec('calc')

can be rendered into HTML equivalent to:

<div title="&amp;" onmouseenter="require('child_process').exec('calc')">

This creates a stored XSS condition. In SiYuan Desktop, the Electron renderer runs with Node.js integration available, so attacker-controlled JavaScript can invoke Node APIs directly. As a result, the issue is not limited to script execution in the page context and becomes arbitrary command execution on the victim’s machine.

The stored XSS path was validated by importing a crafted .sy.zip through the normal GUI and triggering JavaScript execution from the rendered block. Because the same injected JavaScript runs in the privileged Electron renderer, this is an RCE issue in the desktop client.

PoC

  1. Start SiYuan Desktop v3.6.1.
  2. Prepare a crafted .sy.zip containing a .sy document with a block IAL property such as:
"title": "&amp;\" onmouseenter=\"require('child_process').exec('calc')"
  1. In the UI, right-click any notebook.
  2. Select Import -> SiYuan .sy.zip.
  3. Import the crafted archive.
  4. Open the imported note.
  5. Move the mouse over the affected paragraph block.
  6. Observe that the injected JavaScript executes.
  7. On Windows, calc.exe launches, demonstrating arbitrary command execution.

Impact

This vulnerability allows an attacker to deliver a malicious .sy.zip file that executes attacker-controlled JavaScript after import. In the desktop application, that JavaScript runs with Node/Electron privileges and can execute arbitrary operating system commands under the victim’s account. This makes the bug equivalent to local code execution triggered by importing and opening attacker-supplied content.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/siyuan-note/siyuan/kernelall versions0.0.0-20260329142331-918d1bd9f967

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/siyuan-note/siyuan/kernel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/siyuan-note/siyuan/kernel to 0.0.0-20260329142331-918d1bd9f967 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ff66-236v-p4fg is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-ff66-236v-p4fg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-ff66-236v-p4fg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A vulnerability allows crafted block attribute values to bypass server-side attribute escaping when an HTML entity is mixed with raw special characters. An attacker can embed a malicious IAL value inside a `.sy` document, package it as a `.sy.zip`, and have the victim import it through the normal `Import -> SiYuan .sy.zip` workflow. Once the note is opened, the malicious attribute breaks out of its original HTML context and injects an event handler, resulting in stored XSS. In the Electron desktop client, this XSS reaches remote code execution because injected JavaScript runs with
O3 Security · Impact-Aware SCA

Is GHSA-ff66-236v-p4fg in your dependencies?

O3 detects GHSA-ff66-236v-p4fg across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.