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

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

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72795). Confidential information can be exposed externally. Exploitable via POST /api/block/getBlockDOMWithEmbed. Mitigation: upgrade to 0.0.0-20260725125659-1ca1c3c9d94b or later.

Original description

The description as published by the source.

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

Summary

/api/block/getBlockDOMWithEmbed and /api/block/getBlockDOMsWithEmbed gate only the requested block against publish access. The blocks pulled in by that block's embed (transclusion) query are inlined into the returned DOM with no publish-access check at all, so a reader who requests a legitimately-published block containing an embed query receives the content of every block that query matched including blocks in hidden, forbidden and password-protected documents.

The dedicated embed endpoint getEmbedBlock filters these same results for reader roles. The DOM-with-embed path does not.

Details

Item Detail
Routes kernel/api/router.go:226 POST /api/block/getBlockDOMWithEmbed → model.CheckAuth → getBlockDOMWithEmbed; :227 POST /api/block/getBlockDOMsWithEmbed → model.CheckAuth → getBlockDOMsWithEmbed
Middleware CheckAuth only — no CheckReadonly, no CheckAdminRole → reachable by the publish RoleReader token, and anonymously when Publish.Auth.Enable is false
Guard present Top-level requested block only. Singular: password + disable checks on the requested id. Plural: filterBlockDOMsByPublishAccess over the requested ids.
Guard absent The embedded blocks resolved from the query
Exposed Content HTML of every block matched by the embed query, regardless of that block's publish v…

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-72795 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/block/getBlockDOMWithEmbed 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-20260725125659-1ca1c3c9d94b or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72795" on the vendor's site.

CVE-2026-72795 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/block/getBlockDOMWithEmbed / POST /api/block/getBlockDOMsWithEmbed / getEmbedBlock / model.CheckAuth
Patched: 0.0.0-20260725125659-1ca1c3c9d94b — 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-862) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/block/getBlockDOMWithEmbed without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/block/getBlockDOMWithEmbed / POST /api/block/getBlockDOMsWithEmbed / getEmbedBlock / model.CheckAuth.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260725125659-1ca1c3c9d94b.

🛡️ 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/block/getBlockDOMWithEmbed 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/block/getBlockDOMWithEmbed' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/block/getBlockDOMWithEmbed への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260725125659-1ca1c3c9d94b

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/block/getBlockDOMWithEmbed 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-20260725125659-1ca1c3c9d94b"}]}]

References

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