CVE-2026-30869

SiYuan Vulnerable to Path Traversal in /export Endpoint Allows Arbitrary File Read and Secret Leakage

This vulnerability can lead to serious compromise of a SiYuan instance, including:

Arbitrary File Disclosure

• Attackers can read files anywhere on the server filesystem, including system files such as /etc/passwd.

Exposure of Sensitive Secrets

• Configuration files such as conf/conf.json contain sensitive information including:
• API tokens
• cookie signing keys
• workspace authentication codes

Administrative API Access

• Leaked tokens can allow attackers to interact with privileged SiYuan kernel APIs.

Cross‑Origin Localhost Data Exfiltration

• Because the server sets Access-Control-Allow-Origin: *, a malicious website can exploit the vulnerability to read files from a victim's local SiYuan instance running on 127.0.0.1.

Potential Remote Code Execution (RCE)

• Disclosure of authentication secrets and internal configuration may enable attackers to chain this vulnerability with other application features or APIs to achieve remote code execution or full system compromise.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-30869 has a CVSS score of 9.3 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.10); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-30869? CVE-2026-30869 is a critical-severity path traversal vulnerability in github.com/siyuan-note/siyuan/kernel (go), affecting versions <= 3.5.9. It is fixed in 3.5.10. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-30869? CVE-2026-30869 has a CVSS score of 9.3 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/siyuan-note/siyuan/kernel are affected by CVE-2026-30869? github.com/siyuan-note/siyuan/kernel (go) versions <= 3.5.9 is affected.
4. Is there a fix for CVE-2026-30869? Yes. CVE-2026-30869 is fixed in 3.5.10. Upgrade to this version or later.
5. Is CVE-2026-30869 exploitable, and should I be worried? Whether CVE-2026-30869 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-30869 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-30869? Upgrade github.com/siyuan-note/siyuan/kernel to 3.5.10 or later.