SiYuan CVE-2026-59833

Exploitation requires the victim to actively open a poisoned render path - specifically SiYuan's document export-preview or a Bazaar package README render (CVSS UI:A). The payload must reach the victim via attacker-controlled content: a shared or imported note/document, or a Bazaar marketplace package the victim installs and views. The technical prerequisite is that the crafted HTML uses a form action attribute or an SVG xlink:href attribute carrying a javascript: scheme, which Lute's dangerous-scheme block fails to check. RCE (as opposed to mere script execution) is limited to the Electron desktop renderer, so it is users of that desktop build who process untrusted content who are affected; the requirement for victim interaction and attacker-supplied stored content is the primary factor limiting real-world exploitation.

The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H, base 8.6) reflects a network-reachable, low-complexity, unauthenticated payload with high confidentiality, integrity and availability impact, gated only by required user interaction (UI:A) - the victim must open an export-preview or render a Bazaar README. That user-interaction dependency is the single most important limiter and is why this is a serious-but-not-wormable issue: it is stored/persistent XSS delivered through content the target chooses to view, not a drive-by against an exposed service. No EPSS score, SSVC decision, KEV listing, or POC was provided in the input, so exploitation is currently theoretical from an intelligence standpoint (no public exploit identified). The realistic priority is elevated for anyone processing untrusted notes or installing community Bazaar packages, because the Electron renderer turns XSS into RCE; it is lower for isolated single-user instances that never import third-party content. Note the scope question: the vendor scored SC/SI/SA as N even though OS command execution occurs, treating the impact as within the vulnerable desktop application rather than a cross-system scope change - verify with the vendor advisory if scope matters for your scoring.

An attacker crafts a SiYuan note or a Bazaar marketplace package whose README embeds a form action or SVG xlink:href carrying a javascript: payload that survives Lute sanitization. When a victim installs the package or opens the malicious document in export-preview, the payload executes in SiYuan's Electron renderer and runs OS commands on the victim's machine. No public exploit code is identified at time of analysis, and the low attack complexity means a working payload would be straightforward to build once the bypass is understood.