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

Information Disclosure in github.com/siyuan-note/siyuan/kernel (CVE-2026-72804)

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72804). Confidential information can be exposed externally. Exploitable via getGraph. Mitigation: upgrade to 0.0.0-20260724091654-82e9ded423e4 or later.

Original description

The description as published by the source.

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

Summary

getGraph and getLocalGraph filter reader sessions against the visibility tier only and never check the publish password. Password-protected documents are Visible = true, so their graph nodes survive the filter and graph nodes are block-level and carry the block's actual content. An anonymous reader who has never supplied a document's password can therefore retrieve that document's per-block content and its reference/backlink topology. Both endpoints are CheckAuth-only, so they are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false.

Details

Both handlers filter with the invisible-tier set only:

publishIgnore := model.GetInvisiblePublishAccess(publishAccess)   // Visible tier ONLY
nodes, links = model.FilterGraphByPublishIgnore(publishIgnore, nodes, links)

FilterGraphByPublishIgnore (kernel/model/publish_access.go:849) drops a node only when !CheckPathAccessableByPublishIgnore(node.Box, node.Path, publishIgnore). There is no password evaluation anywhere in the graph code grepping graph.go for CheckPublishAuthCookie or password returns nothing.

Because password-protected documents are Visible = true, their nodes pass the filter unchanged.

The nodes carry content, not just titles. genTreeNodes emits one node per block, and nodeTitleLabel sets `node…

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-72804 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like getGraph 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-20260724091654-82e9ded423e4 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72804" on the vendor's site.

CVE-2026-72804 (github.com/siyuan-note/siyuan/kernel) — CWE-200 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: getGraph / getLocalGraph / CheckAuth / RoleReader
Patched: 0.0.0-20260724091654-82e9ded423e4 — 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

Information disclosure (CWE-200) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via getGraph without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: getGraph / getLocalGraph / CheckAuth / RoleReader.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260724091654-82e9ded423e4.

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

  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
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260724091654-82e9ded423e4

    ステージング環境で 0.0.0-20260724091654-82e9ded423e4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

go github.com/siyuan-note/siyuan/kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260724091654-82e9ded423e4"}]}]

References

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