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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-32751: 0.83% estimated exploitation activity in the next 30 days; percentile 57.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Remote Code Execution via Stored XSS in Notebook Name - Mobile Interface Summary SiYuan's 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. Affected Component - Vulnerable file: app/src/mobile/dock/MobileFiles.ts:77 - Safe counterpart: app/src/layout/dock/Files.ts:104 (uses escapeHtml) - Backend (no escaping): kernel/api/notebook.go:104-116 (renameNotebook) -…

Published by the source

16 Mar 2026, 18:47 UTC

Last modified by the source

20 Mar 2026, 21:14 UTC

Source last checked

26 Oct 2026, 15:18 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qr46-rcv3-4hq3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32751

Advisory: SiYuan Vulnerable to Remote Code Execution via Stored XSS in Notebook Name - Mobile Interface
IDs: CVE-2026-32751, GHSA-qr46-rcv3-4hq3
Record: https://patchnext.com/advisories/cve-2026-32751 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected <= 0.0.0-20260313024916-fd6526133bb3

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-qr46-rcv3-4hq3 (GitHub-reviewed advisory GHSA-qr46-rcv3-4hq3 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <=0.0.0-20260313024916-fd6526133bb3)

Commands are suggestions: review each one before running it.