SiYuan searchEmbedBlock SQL injection

Severity: critical · CVSS 10 · Published 2026-08-03

SiYuan is a note-taking application that stores content in a local SQLite database. Versions through 3.7.2 fail to properly restrict access to a search API endpoint that accepts raw SQL queries, allowing unauthenticated users (including readers of published content) to execute arbitrary database operations. An attacker can read sensitive notes and modify or delete content across all unencrypted notebooks without any legitimate access rights.

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

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Critical severity, with a CVSS score of 10, published 3 August 2026.
Which products and versions are affected?
github.com/siyuan-note/siyuan/kernel (Go) < 3.7.3; SiYuan <= 3.7.2.
Is there a fix for This vulnerability?
A patch was published on 2026: Fixed in v3.7.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?
It is attacked over the network, in a web application.
Am I affected?
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.

Technical details

The vulnerability is a SQL injection / unsafe API design flaw in the /api/search/searchEmbedBlock endpoint. The endpoint accepts a "stmt" parameter containing a raw SQL statement and passes it verbatim to SearchEmbedBlock → SearchEmbedBlockInBox → sql.SelectBlocksRawStmtNoParse → query(), which executes the statement on the global read-write siyuan.db handle via the mattn/go-sqlite3 driver. The endpoint is gated only by CheckAuth, making it reachable by publish-mode RoleReader tokens and anonymous users when publish.auth.enable is false. Unlike the guarded /api/query/sql endpoint, searchEmbedBlock lacks CheckSingleStatement, CheckReadonlyStatement, or CheckAdminRole guards. The underlying driver supports stacked statements (separated by semicolons), permitting side effects before post-hoc FilterEmbedBlocksByPublishAccess filtering runs. An unauthenticated attacker can therefore read and write content across all cleartext (unencrypted) notebooks and exploit ATTACH to access filesystem resources. Encrypted per-box notebooks are isolated and excluded. The fix in v3.7.3 applies proper access controls and statement validation.

Affected products

  • SiYuan SiYuan <= 3.7.2

Timeline

  • 2026-07-21: disclosed: Original advisory GHSA-vh22-h7hf-www7 published
  • 2026-08-03: advisory: Duplicate advisory GHSA-p2x7-4c4p-8wh6 published; CVE-2026-69084 assigned
  • 2026: patched: Fixed in v3.7.3

References

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