# CVE-2026-30869: SiYuan has a Path Traversal in /export Endpoint Allows Arbitrary File Read and Secret Leakage

> Attackers can read arbitrary files via path traversal in the export endpoint, leaking secrets that may lead to administrative access or remote code execution.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026
- **Updated:** 10 Mar 2026
- **Also known as:** GHSA-2h2p-mvfx-868w, GO-2026-4646

## What is CVE-2026-30869?

CVE-2026-30869 is a critical path traversal vulnerability in B3log Siyuan, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan is a personal knowledge management system. Prior to 3.5.10, a path traversal vulnerability in the /export endpoint allows an attacker to read arbitrary files from the server filesystem. By exploiting double‑encoded traversal sequences, an attacker can access sensitive files such as conf/conf.json, which contains secrets including the API token, cookie signing key, and workspace access authentication code. Leaking these secrets may enable administrative access to the SiYuan kernel API, and in certain deployment scenarios could potentially be chained into remote code execution (RCE). This vulnerability is fixed in 3.5.10.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-30869?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | None |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.5.10 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 3.5.10 |

Products: B3log Siyuan.

## How do I fix CVE-2026-30869?

Upgrade github.com/siyuan-note/siyuan/kernel to 3.5.10 or later.

## Is CVE-2026-30869 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30869 exists.

## Other vulnerabilities in B3log Siyuan

- [CVE-2026-32938](https://insights.sbomify.com/CVE-2026-32938/): SiYuan has an Arbitrary File Read in its Desktop Publish Service (critical 9.9)
- [CVE-2026-33669](https://insights.sbomify.com/CVE-2026-33669/): SiYuan has Arbitrary Document Reading within the Publishing Service (critical 9.8)
- [CVE-2026-33670](https://insights.sbomify.com/CVE-2026-33670/): SiYuan has directory traversal within its publishing service (critical 9.8)
- [CVE-2026-32767](https://insights.sbomify.com/CVE-2026-32767/): SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API (critical 9.8)
- [CVE-2024-53504](https://insights.sbomify.com/CVE-2024-53504/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30869 and fix it if it is affected.

What it is: CVE-2026-30869 is a critical path traversal vulnerability in B3log Siyuan, published on 9 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30869 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; no fix listed
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.5.10
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 3.5.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30869/ (Markdown: https://insights.sbomify.com/CVE-2026-30869/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30869
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30869
- OSV: https://osv.dev/vulnerability/CVE-2026-30869

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30869/
Summaries are generated and may contain mistakes; the official description above is the record.