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

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

Summary

SQL injection in github.com/siyuan-note/siyuan (CVE-2026-69083). Confidential information can be exposed externally. Exploitable via RoleReader. Mitigation: upgrade to 0.0.0-20260721004815-cf42dd5680c8 or later.

Original description

The description as published by the source.

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

Summary

The /api/search/fullTextSearchAssetContent endpoint exposes two SQL flaws on the asset-content database, both reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false:

  1. method 2 passes a client-supplied SQL statement to the read-write asset-content DB with no single-statement or read-only guard, and without the admin restriction its sibling fullTextSearchBlock applies to the same SQL method.
  2. method 3 builds a REGEXP clause by concatenating the client expression with no quote-escaping, permitting SQL breakout while the equivalent block-search builder does escape.

Both run on a read-write handle through a statement-stacking-capable driver, spanning the cross-notebook asset-content store.

Details

Route / auth tier. router.go: Handle("POST", "/api/search/fullTextSearchAssetContent", model.CheckAuth, fullTextSearchAssetContent), CheckAuth only. Anonymous/reader reachable on the publish surface. parseSearchAssetContentArgs reads method and query straight from the JSON body with no constraint, so both are fully client-controlled.

Missing admin guard (contrast with the sibling). fullTextSearchBlock rejects the SQL method for non-admins (if method == 2 && !IsAdminRoleContext(c)). fullTextSearchAssetContent has no such check on its handler, so the SQL method…

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-69083 has been found in github.com/siyuan-note/siyuan.
Attackers can target a specific entry point like RoleReader 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 to 0.0.0-20260721004815-cf42dd5680c8 or later.
If unsure, ask your IT team or search "github.com/siyuan-note/siyuan CVE-2026-69083" on the vendor's site.

CVE-2026-69083 (github.com/siyuan-note/siyuan) — CWE-89 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RoleReader / Publish.Auth.Enable / false / fullTextSearchBlock
Patched: 0.0.0-20260721004815-cf42dd5680c8 — 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. 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. Attack surface: RoleReader / Publish.Auth.Enable / false / fullTextSearchBlock.

🔥 Severity

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

🔧 How to fix

Update to 0.0.0-20260721004815-cf42dd5680c8.

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

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

  2. 2
    Apply patch patch 
    Upgrade github.com/siyuan-note/siyuan to 0.0.0-20260721004815-cf42dd5680c8

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

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

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

Affected packages

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

References

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