# CVE-2026-59832: Siyuan: Authenticated path traversal in /snippets/ static handler (serveSnippets) leaks conf/conf.json secrets and siyuan.db

> An authenticated attacker can exploit a path traversal flaw in the snippets handler to read sensitive configuration files and the local database.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A: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:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-275h-v5h9-vr82, GO-2026-6350

## What is CVE-2026-59832?

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

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.1, the /snippets/*filepath route handler serveSnippets in kernel/server/serve.go joins a single-decoded request path with the snippets directory without subpath containment or sensitive-path checks, allowing an authenticated request such as /snippets/%2e%2e/%2e%2e/conf/conf.json to read workspace secrets and the document database. This issue is fixed in versions 3.7.1.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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-20260704035520-68cc0f537dfa |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260704035520-68cc0f537dfa |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260704035520-68cc0f537dfa |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260704035520-68cc0f537dfa or later.

## Is CVE-2026-59832 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59832 is a high-severity path traversal vulnerability in siyuan-note siyuan, published on 9 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-59832 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-20260704035520-68cc0f537dfa
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260704035520-68cc0f537dfa
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260704035520-68cc0f537dfa

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

## Sources

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

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