Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72796)
Summary
Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72796). Risk of unauthorized operations or information disclosure. Exploitable via CheckAuth. Mitigation: upgrade to 0.0.0-20260725122641-34be6c0bb073 or later.
Original description
The description as published by the source.
CVE: This vulnerability corresponds to CVE-2026-72796.
Summary
Several static-file routes in the server mux (kernel/server/serve.go) are registered with CheckAuth only and serve directories directly, without the publish-access checks, sensitive-path blocklist, or refuseToAccess rules that the REST API applies to the same data. They are therefore reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false.
Most notably, /templates/ serves data/templates a directory the REST file API explicitly refuses to serve to non-administrators.
Details
| Route | Registration | Guard | Exposed to a reader |
|---|---|---|---|
/templates/* (line 424) |
Group("/templates/", model.CheckAuth).Static("", data/templates) |
none beyond path cleaning | the templates directory |
/snippets/* (line 434) |
CheckAuth |
blocks only conf.json |
any snippet's JS/CSS content by name |
/widgets/, /plugins/, /emojis/ (409/414/419) |
Group(CheckAuth).Static(dir) |
none | whole directory trees |
/export/* (line 320) |
Group("/export/", CheckAuth) |
traversal, sensitive-path and DEK guards: no publish check | export artifacts (PDF/HTML/DOCX/CSV) |
/templates/ directly contradicts an existing control. The REST file path runs refuseToAccess (kernel/api/file.go:551-553), which explicitly returns 403 for data/templates/ to non-administrators t…
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-72796 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like CheckAuth over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725122641-34be6c0bb073 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72796" on the vendor's site.
CVE-2026-72796 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CheckAuth / refuseToAccess / RoleReader / Publish.Auth.Enable
Patched: 0.0.0-20260725122641-34be6c0bb073 — 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.
A vulnerability (CWE-862) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via CheckAuth without authentication.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: CheckAuth / refuseToAccess / RoleReader / Publish.Auth.Enable.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260725122641-34be6c0bb073.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725122641-34be6c0bb073ステージング環境で 0.0.0-20260725122641-34be6c0bb073 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com