Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-73605)
Summary
Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-73605). Risk of unauthorized operations or information disclosure. Exploitable via CheckAuth. Mitigation: upgrade to 0.0.0-20260812083335-251596fc0de2 or later.
Original description
The description as published by the source.
Summary
/api/file/getUniqueFilename takes a path from the request body and passes it to a filesystem existence check with no validation, confinement or authorization. The response distinguishes paths that exist from paths that do not, so an anonymous reader in publish mode can probe arbitrary locations on the host, one request per probe. Files and directories both work.
Every neighbouring file route either requires an administrator or confines the path first.
Details
Route. kernel/api/router.go:289 on master, :292 on the development branch, CheckAuth only.
Handler, kernel/api/file.go:84, in full:
util.ParseJsonArgs(arg, ret, util.BindJsonArg("path", &filePath, true, true))
ret.Data = map[string]any{"path": util.GetUniqueFilename(filePath)}
The argument binder does no path handling. util.BindJsonArg (kernel/util/net.go:365) takes two booleans, required (the key must be present) and rejectEmpty (the value must be non-empty). That is its entire contract. There is no filepath.Clean, no workspace join, no traversal check. An absolute path outside the workspace reaches gulu.File.IsExist unmodified.
The oracle. util/file.go:67:
if !gulu.File.IsExist(filePath) {
return filePath
}
// otherwise loop, returning the first non-existent dir/base (i).ext
Input echoed back means the path does not exist. A (1) suffix means it does.
The asymmetry.
| Route | Middleware |
|---|---|
putFile, copyFile,… |
Source: GitHub Security Advisories (Global) 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-73605 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-20260812083335-251596fc0de2 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-73605" on the vendor's site.
CVE-2026-73605 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CheckAuth / util.BindJsonArg / required / rejectEmpty
Patched: 0.0.0-20260812083335-251596fc0de2 — 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 / util.BindJsonArg / required / rejectEmpty.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260812083335-251596fc0de2.
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-20260812083335-251596fc0de2ステージング環境で 0.0.0-20260812083335-251596fc0de2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web vulncheck.com
- web github.com
- web github.com