SiYuan versions <= 3.8.1 (fixed in v3.8.2) contain an incomplete blocklist in the IsForbiddenAbsPath() function (kernel/util/path_guard.go), which onl...
Description
SiYuan versions <= 3.8.1 (fixed in v3.8.2) contain an incomplete blocklist in the IsForbiddenAbsPath() function (kernel/util/path_guard.go), which only blocks conf/conf.json by exact match and does not restrict the TLS private key (conf/key.pem) or CA private key (conf/ca.key) stored in the same conf/ directory. Because the getFile handler skips the blocklist for RoleAdministrator and all authenticated users receive RoleAdministrator in v3.8.1, any user (or any client on a default no-auth-code instance) can retrieve these private keys via POST /api/file/getFile. On deployments with TLS enabled, this allows decryption of captured HTTPS traffic (key.pem) and forging of certificates trusted by clients that imported SiYuan's CA (ca.key).
AI Analyst Comment
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
Description Summary:
SiYuan versions 3.8.1 and earlier contain an incomplete blocklist in the IsForbiddenAbsPath function, allowing authenticated users to retrieve sensitive TLS and CA private keys.
Executive Summary:
A critical vulnerability in SiYuan versions 3.8.1 and earlier allows authenticated users to access sensitive private keys, potentially leading to full traffic decryption and certificate forgery.
Vulnerability Details
CVE-ID: CVE-2026-85175
Affected Software: siyuan-note siyuan
Affected Versions: 0 up to (excluding) 3.8.2
Vulnerability: The application utilizes an insufficient blocklist within the IsForbiddenAbsPath function, which fails to restrict access to sensitive files like TLS private keys (conf/key.pem) and CA keys (conf/ca.key). Because the getFile handler incorrectly assigns administrative privileges to all authenticated users, any user can retrieve these sensitive keys via the POST /api/file/getFile endpoint.
Business Impact
The compromise of TLS and CA private keys represents a severe security failure that undermines the confidentiality and integrity of all encrypted communication. An attacker possessing these keys can decrypt intercepted HTTPS traffic and issue fraudulent certificates that appear trusted by clients, resulting in significant data exposure, credential theft, and total loss of communication privacy. With a CVSS score of 8.8, this high severity vulnerability necessitates immediate attention to prevent lateral movement and broader system compromise.
Remediation Plan
Immediate Action: Upgrade to SiYuan version 3.8.2 or later to apply the necessary security patches and blocklist updates.
Proactive Monitoring: Review access logs for the /api/file/getFile endpoint, specifically monitoring for unauthorized or suspicious requests originating from standard user accounts.
Compensating Controls: Restrict network access to the SiYuan administrative interface and sensitive API endpoints using a Web Application Firewall or network segmentation to prevent exploitation by unauthorized actors.
Exploitation Status
Public Exploit Available: Unknown
Analyst Notes: As of September 4, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The flaw is inherently dangerous due to the ease with which administrative access is granted to all authenticated users, enabling the retrieval of highly sensitive cryptographic material.
Analyst Recommendation
Given the potential for total compromise of encrypted sessions and certificate authority integrity, organizations must prioritize upgrading to version 3.8.2 immediately. Ensure that the patch is applied across all instances of the application, particularly those with TLS enabled, to mitigate the risk of traffic interception and certificate forgery.