← Back
CVE-2026-41894
Path Traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-41894)
Summary
path traversal in github.com/siyuan-note/siyuan/kernel (CVE-2026-41894). Risk of unauthorized operations or information disclosure. Exploitable via `GET /export/`. Mitigation: upgrade to `3.6.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41894** has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like `GET /export/` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to **3.6.5** or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-41894" on the vendor's site.
CVE-2026-41894 (github.com/siyuan-note/siyuan/kernel) — CWE-22 /
Attack surface: GET /export/ / `IsSensitivePath` / `siyuan.db` / `siyuan.log`
Patched: `3.6.5` — 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.
❓ What is the problem
**Path traversal** (CWE-22) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via `GET /export/` without authentication.
📍 Affected scope
github.com/siyuan-note/siyuan/kernel — . Attack surface: GET /export/ / `IsSensitivePath` / `siyuan.db` / `siyuan.log`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.6.5**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /export/` 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /export/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /export/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/siyuan-note/siyuan/kernel to 3.6.5ステージング環境で 3.6.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /export/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/siyuan-note/siyuan/kernel
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.6.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41894
- advisory https://github.com/advisories/GHSA-2h2p-mvfx-868w
- package https://github.com/siyuan-note/siyuan
- web https://github.com/siyuan-note/siyuan/security/advisories/GHSA-hjh7-r5w8-5872
- web https://github.com/siyuan-note/siyuan/commit/bb481e1290c4a34255652ede85a546504505d2a7
- web https://github.com/siyuan-note/siyuan/releases/tag/v3.6.5