Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-72794 high CVSS 8.6

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72794)

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72794). Confidential information can be exposed externally. Exploitable via POST /api/system/getConf. Mitigation: upgrade to 0.0.0-20260725123945-77421530be4a or later.

Original description

The description as published by the source.

CVE: This vulnerability corresponds to CVE-2026-72794.

Summary

/api/system/getConf returns Conf.CookieKey, the key used to sign the server's session cookies in its response body. The endpoint is registered with CheckAuth only, so the field reaches the publish RoleReader token and the anonymous account when Publish.Auth.Enable is false.

The configuration-export endpoint in the same file strips this exact field before returning config, so the project already treats it as secret. The reader-facing masking path does not.

Details

Item Detail
Route kernel/api/router.go:70 POST /api/system/getConf → model.CheckAuth → getConf
Middleware CheckAuth only — no CheckReadonly, no CheckAdminRole
Leaked field AppConf.CookieKey, serialized as cookieKey
Purpose of the field Signing key for the siyuan session cookie

The field survives every stage of the masking chain. getConf masks through GetMaskedConf() → HideConfSecret() (non-administrators) → FilterConfByPublishIgnore() (readers) → the browser-side System-path strip. CookieKey is removed by none of them:

  • GetMaskedConf masks UserData, MCPOAuth and AccessAuthCode only.
  • HideConfSecret nulls AI, Api, Flashcard, ServerAddrs, Publish, Repo, Sync, Secrets, Variables and the System paths. It contains no reference to CookieKey.
  • FilterConfByPublishIgnore touch…

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-72794 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: 8.6/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725123945-77421530be4a or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72794" on the vendor's site.

CVE-2026-72794 (github.com/siyuan-note/siyuan/kernel) — CWE-522 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/system/getConf / Conf.CookieKey / CheckAuth / RoleReader
Patched: 0.0.0-20260725123945-77421530be4a — 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

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.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/system/getConf / Conf.CookieKey / CheckAuth / RoleReader.

🔥 Severity

Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260725123945-77421530be4a.

🛡️ 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 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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt 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 があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725123945-77421530be4a

    ステージング環境で 0.0.0-20260725123945-77421530be4a に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/system/getConf on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/siyuan-note/siyuan/kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260725123945-77421530be4a"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details