CVE-2026-100638 in SiYuan
Summary
by MITRE • 09/26/2026
SiYuan versions before v3.8.4 contain a path traversal vulnerability in the setNotebookIcon endpoint that allows authenticated administrators to create arbitrary directory trees and write files outside the workspace boundary. Attackers can supply directory traversal sequences in the notebook parameter to escape the workspace data directory and write conf.json files to arbitrary locations accessible by the kernel process.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 09/26/2026
The vulnerability identified in SiYuan versions prior to v3.8.4 represents a critical path traversal flaw located within the setNotebookIcon endpoint of the application's API layer. This security defect arises from insufficient validation and sanitization of user-supplied input, specifically the notebook parameter passed during icon configuration requests. Although the vulnerability requires authentication as an administrator, this high-privilege requirement does not mitigate the severity because it allows for significant lateral movement or privilege escalation within the system context in which SiYuan operates. The core technical failure lies in the application's inability to properly canonicalize and restrict file paths relative to the designated workspace directory, thereby permitting attackers to utilize standard directory traversal sequences such as dot-dot-slash to navigate up the filesystem hierarchy beyond the intended sandbox boundaries.
From a technical perspective, this flaw enables an authenticated administrator to manipulate the underlying file system structure by creating arbitrary directory trees outside of the secure workspace container. By injecting path traversal characters into the notebook identifier, the attacker can direct write operations to locations that are accessible and writable by the SiYuan kernel process. This capability is particularly dangerous because it allows for the creation of configuration files in sensitive directories where the application reads settings upon startup or during runtime execution. The ability to write arbitrary content to these external paths effectively breaks the isolation model intended to protect user data from cross-workspace contamination or unauthorized system modification, turning a simple icon update feature into a mechanism for persistent file system manipulation.
The operational impact of this vulnerability is substantial, primarily due to the potential for remote code execution through configuration poisoning. By writing malicious conf.json files to locations that are subsequently loaded by the kernel process, an attacker can inject arbitrary logic or alter critical application settings. Since SiYuan often runs with elevated privileges relative to standard user applications to facilitate file system access and plugin loading, successfully exploiting this path traversal could allow an attacker to execute code under those same privileged conditions. This transforms a local administrative action into a potential vector for full system compromise, depending on the deployment environment and the specific permissions granted to the SiYuan process. The ability to write files outside the workspace also poses risks related to data integrity and confidentiality, as it may allow overwriting of other application configuration files or sensitive user documents stored in adjacent directories.
This vulnerability aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which describes flaws where software does not properly neutralize special elements within file names that can cause unintended directory traversal. Furthermore, the exploitation technique maps directly to ATT&CK T1553.004: Subvert Trust Controls, specifically through Marking File for Execution or modifying configuration files to bypass security mechanisms. The attack pattern also reflects CWE-94: Improper Control of Generation of Code (Code Injection), as writing malicious configurations that are then interpreted by the kernel constitutes a form of code injection via data manipulation.
Mitigation strategies must prioritize immediate patching to version v3.8.4 or later, where this input validation issue has been addressed. In environments where upgrading is not immediately feasible, administrators should implement strict network-level access controls to restrict API endpoints to only trusted internal sources and enforce multi-factor authentication for all administrative accounts to reduce the attack surface. Additionally, running SiYuan with least-privilege principles can limit the impact of successful exploitation by ensuring that even if arbitrary files are written, they cannot be executed or interpreted as code by the kernel process. Regular auditing of file system permissions and monitoring for unusual write operations outside designated workspace directories can also aid in early detection of such traversal attempts.