CVE-2026-74801

CVE-2026-74801 is a path injection vulnerability in SiYuan's elevated helper (elevator.exe) that executes when configuring Windows Defender exclusions. The application legitimately requires administrator privileges to add folder exclusions, but it passes the workspace path to this elevated process without proper sanitization, allowing command injection. The conventional analysis will focus on the two-UAC-prompt prerequisite — victim opens a malicious workspace, approves elevation twice — but this understates the actual attack surface. SiYuan supports workspace sharing and importing in a community where users routinely exchange notebooks and configurations. An attacker can pre-populate a victim's environment with a crafted workspace name that sits dormant until the Defender exclusion feature is invoked. The trigger is not 'trick the user twice' but rather 'have a malicious workspace exist when any elevated operation occurs.' Users who imported a workspace months ago and forgot about it become vulnerable the moment they use the exclusion feature for any purpose. The blast radius matters more than the injection itself. SiYuan users are knowledge workers — developers with source code, architects with design documents, researchers with API keys stored in notes. Compromising an elevated process doesn't just give you local code execution; it gives you the ability to modify Windows Defender exclusions directly, disabling detection for everything that follows. That's not lateral movement — that's turning off the alarm before entering. The patch description mentions 'properly escape,' which is a fix-level signal worth examining. Escaping or quoting the path is a locally-correct but globally-fragile fix — it patches the symptom while preserving the architectural vulnerability. The structurally correct fix moves the workspace path out of the command line entirely. If the commit shows only added escaping, expect similar vulnerabilities in future features that use the elevated helper. The pattern of elevated-helper-plus-path-injection has appeared in other productivity tools; it's a structural consequence of wrapping privileged operations in UI that accepts user-controlled filesystem data, not a simple coding mistake.

Reviewed through automated stages and approved by a human before publication.