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

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

Summary

Vulnerability in github.com/siyuan-note/siyuan/kernel (CVE-2026-72810). Confidential information can be exposed externally. Exploitable via RoleReader. Mitigation: upgrade to 0.0.0-20260723013612-ba948639d7f6 or later.

Original description

The description as published by the source.

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

Summary

WebSocket sessions established through the publish surface (port 6808, RoleReader anonymous when Publish.Auth.Enable is false) are added to the same broadcast session pool as authenticated sessions. The kernel's broadcast functions push content events transactions carrying block DOM, document save/create, move/rename to every session in the pool with no role or publish-access filtering. As a result, an anonymous reader who holds a WebSocket connection open passively receives a real-time feed of every edit made in the workspace, including edits to password-protected, publish-forbidden, and unpublished documents. Because these events are delivered over the push channel and never pass through an HTTP handler, none of the publish-access filters that gate the HTTP endpoints apply.

Details

Session admission. HandleConnect admits the injected RoleReader publish token, and the session is registered via AddPushChan into the same sessions pool used for authenticated clients.

Unfiltered broadcast. The broadcast functions (Broadcast, broadcastOthers, broadcastOtherAppMains, …) write to every session in the pool with no role or publish-access check. The isPublish flag on a session is consulted only to send the "service closed" notice it is never used to gate content. Content events are pushed via PushModeBroadcast → Broadcast(),…

Source: GitHub Security Advisories (Global) 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-72810 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like RoleReader 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-20260723013612-ba948639d7f6 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-72810" on the vendor's site.

CVE-2026-72810 (github.com/siyuan-note/siyuan/kernel) — CWE-862 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RoleReader / Publish.Auth.Enable / false / HandleConnect
Patched: 0.0.0-20260723013612-ba948639d7f6 — 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 RoleReader without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: RoleReader / Publish.Auth.Enable / false / HandleConnect.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260723013612-ba948639d7f6.

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

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

  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-20260723013612-ba948639d7f6"}]}]

References

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