CVE-2026-32751 SiYuan Vulnerable to Remote Code Execution via Stored XSS in Notebook Name - Mobile Interface

Medium 5.1 Published Updated

Authenticated attackers can inject JavaScript via notebook names, leading to remote code execution on mobile and desktop clients due to unsafe innerHTML usage and Electron configuration.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-32751?

CVE-2026-32751 is a medium-severity cross-site scripting vulnerability in B3log Siyuan, published on 19 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

SiYuan is a personal knowledge management system. In versions 3.6.0 and below, the mobile file tree (MobileFiles.ts) renders notebook names via innerHTML without HTML escaping when processing renamenotebook WebSocket events. The desktop version (Files.ts) properly uses escapeHtml() for the same operation. An authenticated user who can rename notebooks can inject arbitrary HTML/JavaScript that executes on any mobile client viewing the file tree. Since Electron is configured with nodeIntegration: true and contextIsolation: false, the injected JavaScript has full Node.js access, escalating stored XSS to full remote code execution. The mobile layout is also used in the Electron desktop app when the window is narrow, making this exploitable on desktop as well. This issue has been fixed in version 3.6.1.

Weakness: CWE-79

Which versions are affected by CVE-2026-32751?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product.

PackageAffectedFixed in
github.com/siyuan-note/siyuan/kernel GoAll versionsNone
github.com/siyuan-note/siyuan/kernel GoAll versions to 0.0.0-20260313024916-fd6526133bb3None
github.com/siyuan-note/siyuan/kernel GoAll versions to 0.0.0-20260313024916-fd6526133bb3None

Products include B3log Siyuan.

How do I fix CVE-2026-32751?

Upgrade to a fixed version.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-32751 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32751 exists.

All B3log Siyuan vulnerabilities

Sources

Also known as GHSA-qr46-rcv3-4hq3, GO-2026-4706.

Is CVE-2026-32751 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free