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

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

Summary

SQL injection in github.com/siyuan-note/siyuan/kernel (CVE-2026-72811). Confidential information can be exposed externally. Exploitable via MATCH. Mitigation: upgrade to 0.0.0-20260723004839-1a5b3431d5ab or later.

Original description

The description as published by the source.

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

Summary

The backlink/mention search query (kernel/model/backlink.go) concatenates stored block metadata (title, name, alias, anchor text) and the client-supplied keyword into a SQL MATCH/search statement, escaping only the double-quote character (") and not the single quote ('). A single quote in either the client keyword or in stored document metadata breaks out of the string literal. The query runs on the main read-write siyuan.db handle through a statement-stacking-capable driver.

This yields two vectors:

  • First-order: a client-supplied keyword containing ' injects directly. This path is reachable by an anonymous reader on the publish surface.
  • Second-order: a document whose title/name/alias contains ' is stored safely (indexing uses parameterized inserts) but detonates when that stored value is later concatenated into the backlink query including on another user's kernel that has ingested the malicious document.

Details

Storage is safe; reuse is not. Indexing INSERTs (kernel/sql/upsert.go) are parameterized ((?,?,…) with bound arguments for Name/Content/Markdown/IAL), so malicious .sy content is stored intact and safely. The injection is in the reuse path: the backlink/mention MATCH query (kernel/model/backlink.go, around line 980) builds its condition by concatenating the stored title/name/alias/anchor an…

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

CVE-2026-72811 (github.com/siyuan-note/siyuan/kernel) — CWE-89 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: MATCH / siyuan.db / Name / Content
Patched: 0.0.0-20260723004839-1a5b3431d5ab — 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 MATCH without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/siyuan-note/siyuan/kernel. Attack surface: MATCH / siyuan.db / Name / Content.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260723004839-1a5b3431d5ab.

🛡️ 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-20260723004839-1a5b3431d5ab

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

  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-20260723004839-1a5b3431d5ab"}]}]

References

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