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

Vulnerability in siyuan (CVE-2026-68586)

Summary

Vulnerability in siyuan (CVE-2026-68586). Confidential information can be exposed externally. Exploitable via CheckAuth. Mitigation: upgrade to 0.0.0-20260721014413-f45749a7ef6e or later.

Original description

The description as published by the source.

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

Summary

The backlink API splits into list endpoints (which documents reference a block) and content endpoints (the rendered text of those referencing blocks). The list endpoints apply a publish-access filter, the content endpoints do not. As a result, /api/ref/getBacklinkDoc and /api/ref/getBackmentionDoc return the rendered DOM of blocks belonging to a publish-forbidden document to an anonymous reader, with no access check.

Both content endpoints are gated by CheckAuth only, reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false.

Details

The asymmetry between the list and content sides is the tell that this is an oversight, not intended behavior:

Endpoint Returns Publish-access filter Route
getBacklink list (*Path) FilterPathsByPublishAccess - present CheckAuth
getBacklink2 list (*Path) FilterPathsByPublishAccess - present CheckAuth
getBacklinkDoc rendered DOM none CheckAuth
getBackmentionDoc rendered DOM none CheckAuth

model/backlink.go contains no publish-access reference anywhere, and Backlink.DOM is the rendered HTML of the referencing blocks. getBacklinkDoc(defID, refTreeID) returns the rendered content of blocks in refTreeID - including a publish-forbidden, publish-disabled, or password-…

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-68586 has been found in siyuan.
Attackers can target a specific entry point like CheckAuth over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade siyuan to 0.0.0-20260721014413-f45749a7ef6e or later.
If unsure, ask your IT team or search "siyuan CVE-2026-68586" on the vendor's site.

CVE-2026-68586 (siyuan) — CWE-862 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CheckAuth / RoleReader / Publish.Auth.Enable / false
Patched: 0.0.0-20260721014413-f45749a7ef6e — 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 siyuan. Attackers reach the vulnerable code path via CheckAuth without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of siyuan. Attack surface: CheckAuth / RoleReader / Publish.Auth.Enable / false.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260721014413-f45749a7ef6e.

🛡️ 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 'siyuan' . 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 'siyuan' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で siyuan を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade siyuan to 0.0.0-20260721014413-f45749a7ef6e

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

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

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

Affected packages

npm siyuan
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
go github.com/siyuan-note/siyuan/kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260721014413-f45749a7ef6e"}]}]

References

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