Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-69085 critical CVSS 10.0

SQL Injection in github.com/siyuan-note/siyuan/kernel (CVE-2026-69085)

Summary

SQL injection in github.com/siyuan-note/siyuan/kernel (CVE-2026-69085). Confidential information can be exposed externally. Exploitable via POST /api/notebook/lsNotebooks. Mitigation: upgrade to 0.0.0-20260721043339-eef10568384e or later.

Original description

The description as published by the source.

Summary

The /api/filetree/searchDocs endpoint concatenates the caller-supplied search keyword directly into a SQL statement with no escaping and no parameter binding. The endpoint is gated by CheckAuth only reachable by the publish RoleReader token, and by the anonymous account when Publish.Auth.Enable is false. The resulting statement runs on a read-write SQLite handle through a driver that executes stacked (;-separated) statements, against the global blocks table spanning all cleartext notebooks. An unauthenticated request can therefore read and write database content across every non-encrypted notebook on the instance.

Details

Data flow, unescaped and unbound at every hop:

  • searchDocs (kernel/api/filetree.go): k := arg["k"].(string) passed straight to model.SearchDocs(k, …), no sanitization.
  • SearchDocs (kernel/model/file.go): after TrimSpace and strings.Fields, each token is spliced into a single-quoted LIKE literal by concatenation condition.WriteString("(hpath LIKE '%" + k + "%'"). No escaping, no '' doubling, no bind placeholder.
  • NAMFilter (kernel/conf/search.go): appends " OR name LIKE '%" + keyword + "%'" (and alias, memo) the same way, enabled by default.
  • QueryRootBlockByCondition (kernel/sql/block_query.go): "SELECT *, … FROM blocks WHERE type = 'd' AND " + condition + " ORDER BY … LIMIT …" passed to query(sqlStmt).

The only value-inspecting guard is ast.IsNodeIDPattern(keyword), which merely…

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-69085 has been found in github.com/siyuan-note/siyuan/kernel.
Attackers can target a specific entry point like POST /api/notebook/lsNotebooks over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 10.0/10.
What to do: upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721043339-eef10568384e or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan/kernel CVE-2026-69085" on the vendor's site.

CVE-2026-69085 (github.com/siyuan-note/siyuan/kernel) — CWE-89 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/notebook/lsNotebooks / CheckAuth / Publish.Auth.Enable / false
Patched: 0.0.0-20260721043339-eef10568384e — 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

SQL injection (CWE-89) exists in github.com/siyuan-note/siyuan/kernel. Attackers reach the vulnerable code path via POST /api/notebook/lsNotebooks without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: POST /api/notebook/lsNotebooks / CheckAuth / Publish.Auth.Enable / false.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.0.0-20260721043339-eef10568384e.

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

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

  3. 3
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721043339-eef10568384e

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

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

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

Affected packages

go github.com/siyuan-note/siyuan/kernel
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.0-20260721043339-eef10568384e"}]}]

References

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