Path Traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-59832)
Summary
Path traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-59832). Confidential information can be exposed externally. Exploitable via GET /snippets/. Mitigation: upgrade to 0.0.0-20260704035520-68cc0f537dfa or later.
Original description
The description as published by the source.
Reporter: Cavan Loughran, Celvex Group Inc.
Summary
The /snippets/*filepath route handler serveSnippets in kernel/server/serve.go performs a bare filepath.Join(util.SnippetsPath, filePath) on the single-decoded c.Request.URL.Path and serves the result with c.File(), with NO IsSubPath containment and NO IsSensitivePath denylist - unlike the sibling /export/ (serveExport) and /appearance/ (serveAppearance) handlers, which both carry IsSubPath, and unlike /assets/ (serveAssets), whose traversal was fixed in GHSA-p4m3-mgmm-c664. Because util.SnippetsPath = WorkspaceDir/data/snippets, an authenticated request to GET /snippets/%2e%2e/%2e%2e/conf/conf.json resolves to WorkspaceDir/conf/conf.json and leaks the kernel API token and AccessAuthCode (the same secret file CVE-2026-30869 leaked from /export/); GET /snippets/%2e%2e/%2e%2e/temp/siyuan.db leaks the full document database.
Affected versions
v3.6.5 and current master (verified by direct source read). The /export/ and /assets/ fixes were endpoint-scoped and never reached serveSnippets.
Technical detail
Sink, kernel/server/serve.go, serveSnippets (verbatim, current master and v3.6.5):
func serveSnippets(ginServer *gin.Engine) {
ginServer.Handle("GET", "/snippets/*filepath", model.CheckAuth, func(c *gin.Context) {
filePath := strings.TrimPrefix(c.Request.URL.Path, "/snippets/")
if !model.IsAdminRoleContext(c) {
if "conf.json" == filePath {…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-59832 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like GET /snippets/ over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260704035520-68cc0f537dfa or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-59832" on the vendor's site.
CVE-2026-59832 (github.com/siyuan-note/siyuan/kernel) — CWE-22 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /snippets/
Patched: 0.0.0-20260704035520-68cc0f537dfa — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via GET /snippets/.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: GET /snippets/.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 0.0.0-20260704035520-68cc0f537dfa.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /snippets/ requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/siyuan-note/siyuan/kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/siyuan-note/siyuan/kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/siyuan-note/siyuan/kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /snippets/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /snippets/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260704035520-68cc0f537dfaステージング環境で 0.0.0-20260704035520-68cc0f537dfa に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /snippets/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com