Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72805)
Summary
Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72805). Risk of unauthorized operations or information disclosure. Exploitable via getBlockInfo. Mitigation: upgrade to 0.0.0-20260723163028-931ba693375e or later.
Original description
The description as published by the source.
CVE: This vulnerability corresponds to CVE-2026-72805.
Summary
Three block endpoints return document content snippets and metadata without any publish-access check, while their sibling getBlockInfo which returns comparable data does enforce one. All three are CheckAuth-only, so they are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. An anonymous reader supplying a block ID receives content and metadata belonging to publish-forbidden and password-protected documents.
Details
getBlockInfo (kernel/api/block.go) gates on the publish boundary:
if !checkBlockPublishAccess(c, id, ret) {
return
}
The following siblings in the same file perform no equivalent check:
| Endpoint | Returns | Publish check |
|---|---|---|
getBlockInfo |
root/title/path metadata | checkBlockPublishAccess: present |
getBlockBreadcrumb |
BlockPath.Name : root document title plus every ancestor block's content snippet |
none |
getRefText |
the block's reference/anchor text (document content) | none |
getBlockTreeInfos |
root/title/path metadata for arbitrary block IDs | none |
getBlockBreadcrumb returns the full ancestor chain including each ancestor block's content snippet, and getRefText returns block anchor text both are document content, not just metadata. getBlockTreeInfos returns root/title/path for any caller-supplied ID se…
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-72805 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like getBlockInfo 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-20260723163028-931ba693375e or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72805" on the vendor's site.
CVE-2026-72805 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 5.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getBlockInfo / CheckAuth / RoleReader / Publish.Auth.Enable
Patched: 0.0.0-20260723163028-931ba693375e — 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 getBlockInfo without authentication.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: getBlockInfo / CheckAuth / RoleReader / Publish.Auth.Enable.
Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.
Update to 0.0.0-20260723163028-931ba693375e.
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-20260723163028-931ba693375eステージング環境で 0.0.0-20260723163028-931ba693375e に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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