CVE-2026-69083: SiYuan fullTextSearchAssetContent SQL injection and REGEXP breakout

CVE-2026-69083 · Severity: critical · CVSS 10 · Published 2026-09-03

SiYuan is a note-taking and knowledge management application. An unauthenticated attacker or any reader in publish mode can exploit two SQL flaws in the asset content search endpoint to execute arbitrary SQL queries, read sensitive data across all notebooks, and modify database records. The vulnerability bypasses authentication and permission checks, allowing unauthorized access to content that should be restricted from public viewing.

Technologies: github.com/siyuan-note/siyuan/kernel (Go), SiYuan. Vendors: Go, SiYuan.

Quick answers

Is CVE-2026-69083 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-69083 being exploited in the wild.
How severe is CVE-2026-69083?
Critical severity, with a CVSS score of 10, published 3 September 2026.
Which products and versions are affected?
github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260721004815-cf42dd5680c8, SEMVER:introduced=0,fixed=0.0.0-20260721004815-cf42dd5680c8; SiYuan before 0.0.0-20260721004815-cf42dd5680c8.
Is there a fix for CVE-2026-69083?
Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721004815-cf42dd5680c8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69083 attacked?
It is attacked over the network.
Am I affected by CVE-2026-69083?
Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260721004815-cf42dd5680c8 or later
    go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260721004815-cf42dd5680c8

Technical details

The vulnerability comprises two SQL injection attack paths in the `/api/search/fullTextSearchAssetContent` endpoint. Method 2 accepts client-controlled SQL statements and passes them directly to `assetContentDB.Query()` without single-statement or read-only validation, and without the admin-role check that its sibling `fullTextSearchBlock` applies. Method 3 concatenates user-supplied REGEXP expressions into SQL without quote-escaping (unlike the parallel block-search builder), allowing SQL breakout via `'` characters. Both paths operate on a read-write SQLite handle with statement-stacking capability and ATTACH support, spanning cross-notebook asset-content storage. The endpoint requires only `CheckAuth` (satisfied by anonymous access when auth is disabled or any publish reader token), and post-hoc permission filtering runs after query execution, providing no defense. Patched in commit cf42dd5680c8.

Affected products

  • siyuan-note siyuan before 0.0.0-20260721004815-cf42dd5680c8

Identifiers

  • CVE-2026-69083
  • GHSA-fph3-ghq9-vw66
  • GO-2026-6374

Timeline

  • 2026-09-03: advisory
  • 2026-07-21: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.