# CVE-2026-34585: SiYuan: Stored XSS in imported .sy.zip content leads to arbitrary command execution > Attackers can achieve remote code execution in the Electron client by tricking users into importing malicious .sy.zip files containing stored XSS payloads. - **Severity:** High 8.6 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 31 Mar 2026 - **Updated:** 1 Apr 2026 - **Also known as:** GHSA-ff66-236v-p4fg, GO-2026-5357 ## What is CVE-2026-34585? CVE-2026-34585 is a high-severity cross-site scripting vulnerability in B3log Siyuan, published on 31 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description SiYuan is a personal knowledge management system. Prior to version 3.6.2, 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. This issue has been patched in version 3.6.2. Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2026-34585? 3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260329142331-918d1bd9f967 | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260329142331-918d1bd9f967 | | `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260329142331-918d1bd9f967 | Products: B3log Siyuan. ## How do I fix CVE-2026-34585? Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260329142331-918d1bd9f967 or later. ## Is CVE-2026-34585 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34585 exists. ## Other vulnerabilities in B3log Siyuan - [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9) - [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8) - [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8) - [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8) - [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-34585 and fix it if it is affected. What it is: CVE-2026-34585 is a high-severity cross-site scripting vulnerability in B3log Siyuan, published on 31 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34585 exists. Affected packages and fixed versions: - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260329142331-918d1bd9f967 - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260329142331-918d1bd9f967 - github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260329142331-918d1bd9f967 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-34585/ (Markdown: https://insights.sbomify.com/CVE-2026-34585/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34585 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34585 - OSV: https://osv.dev/vulnerability/CVE-2026-34585 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-34585/ Summaries are generated and may contain mistakes; the official description above is the record.