# CVE-2026-65607: SiYuan before v3.7.2 Path Traversal via /export/temp/

> An authenticated attacker can exploit a path traversal flaw in the export handler to read arbitrary files, including sensitive system and workspace data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-2vq9-c755-fq2h, GHSA-gw25-m53r-qh88, GO-2026-6365

## What is CVE-2026-65607?

CVE-2026-65607 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SiYuan before v3.7.2 contains a path traversal vulnerability in the /export/temp/ short-circuit branch of the serveExport handler (kernel/server/serve.go). Unlike the main export branch, this branch joins the raw, percent-decoded request path with util.TempDir and serves the file without the IsSubPath or IsSensitivePath checks added in the earlier export-disclosure hardening (GHSA-6865-qjcf-286f). An authenticated attacker can send percent-encoded traversal sequences (e.g. /export/temp/%2e%2e/.../etc/passwd, where %2e%2e is decoded to '..') to read arbitrary files outside TempDir, including /etc/passwd, SSH keys (~/.ssh/*), and SiYuan workspace *.db and *.log files, bypassing the sensitive-file protection.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260510110132-b763d787d1f2 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260510110132-b763d787d1f2 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260510110132-b763d787d1f2 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260510110132-b763d787d1f2 or later.

## Is CVE-2026-65607 being exploited?

There is no known exploitation of CVE-2026-65607 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65607 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65607 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260510110132-b763d787d1f2
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260510110132-b763d787d1f2
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260510110132-b763d787d1f2

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-65607/ (Markdown: https://insights.sbomify.com/CVE-2026-65607/index.md)
```

## Sources

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

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