Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72801)
Summary
Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72801). Confidential information can be exposed externally. Exploitable via POST /api/system/getConf. Mitigation: upgrade to 0.0.0-20260724102025-3bc014c7dc32 or later.
Original description
The description as published by the source.
CVE: This vulnerability corresponds to CVE-2026-72801.
Summary
Two CheckAuth-only endpoints disclose the complete offline attack material for the encrypted-notebook master password, plus the wrapped per-notebook key needed to use it. Both are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. An unauthenticated remote client can retrieve the Argon2id salt and cost parameters, a verifier that confirms a correct password offline, and the encrypted per-notebook data key reducing the security of every encrypted notebook to the master password's resistance to offline GPU cracking.
Details
(1) POST /api/system/getConf leaks NotebookCrypto.
getConf → GetMaskedConf() marshals the full configuration including NotebookCrypto *conf.NotebookCrypto (JSON tag notebookCrypto, not -, so it survives the deep copy). For non-administrators HideConfSecret() is applied, which nulls a dozen secret-bearing fields like AI, MCPOAuth, Api, Flashcard, Publish, Repo, Sync, Secrets, Variables, System paths but contains no reference to NotebookCrypto. FilterConfByPublishIgnore() for readers only touches UILayout.
The reader therefore receives:
| Field | What it is |
|---|---|
MasterSalt |
global Argon2id salt |
KDFParams |
Argon2id memory/time/parallelism cost |
KEKVerifier + VerifierNonce |
AES-GCM-encrypted fixed magic, the in-co… |
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-72801 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/system/getConf over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724102025-3bc014c7dc32 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72801" on the vendor's site.
CVE-2026-72801 (github.com/siyuan-note/siyuan/kernel) — CWE-522 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/system/getConf / POST /api/notebook/getNotebookConf / CheckAuth / RoleReader
Patched: 0.0.0-20260724102025-3bc014c7dc32 — 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-522) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/system/getConf without authentication.
Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/system/getConf / POST /api/notebook/getNotebookConf / CheckAuth / RoleReader.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.0.0-20260724102025-3bc014c7dc32.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/system/getConf 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 'POST /api/system/getConf' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/system/getConfへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724102025-3bc014c7dc32ステージング環境で 0.0.0-20260724102025-3bc014c7dc32 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/system/getConf on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com