SiYuan: Unauthenticated arbitrary SQL execution via searchEmbedBlock (publish mode) : reader-reachable raw statement on read-write handle, cross-notebook read/write

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-69084: 1.57% estimated exploitation activity in the next 30 days; percentile 75.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CVE: This vulnerability corresponds to CVE-2026-69084. Summary The /api/search/searchEmbedBlock endpoint passes a client-supplied SQL statement verbatim to the database with no validation. 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 statement runs on the main read-write siyuan.db handle through a driver that executes stacked statements, with no single-statement or read-only guard. An unauthenticated request can therefore execute arbitrary SQL reading and writing content across all cleartext notebooks. Unlike SQL injection into a fixed query, this endpoint accepts a full SQL statement by design and simply fails to restrict who may call it or what the statement may do. Details Data flow verbatim, unvalidated: - searchEmbedBlock (kernel/api/search.go): stmt := arg["stmt"].(string) passed directly to model.SearchEmbedBlock(stmt, …). No validation. - SearchEmbedBlock →…

Published by the source

3 Sep 2026, 20:19 UTC

Last modified by the source

10 Sep 2026, 15:15 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-vh22-h7hf-www7

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6377

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-vh22-h7hf-www7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-69084

Advisory: SiYuan: Unauthenticated arbitrary SQL execution via searchEmbedBlock (publish mode) : reader-reachable raw statement on read-write handle, cross-notebook read/write
IDs: CVE-2026-69084, GHSA-vh22-h7hf-www7
Record: https://patchnext.com/advisories/cve-2026-69084 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260721002947-23a17d44b5f3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260721002947-23a17d44b5f3; fixed in 0.0.0-20260721002947-23a17d44b5f3

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vh22-h7hf-www7 (OSV record GHSA-vh22-h7hf-www7 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721002947-23a17d44b5f3 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6377 (OSV record GO-2026-6377 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721002947-23a17d44b5f3 (fixed))
- Verified: https://github.com/advisories/GHSA-vh22-h7hf-www7 (GitHub-reviewed advisory GHSA-vh22-h7hf-www7 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721002947-23a17d44b5f3)

Commands are suggestions: review each one before running it.