SiYuan: Unauthenticated SQL injection in searchDocs via unescaped keyword (publish mode): cross-notebook read/write with statement stacking

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-69085: 1.39% estimated exploitation activity in the next 30 days; percentile 72.36 (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.

Summary The /api/filetree/searchDocs endpoint concatenates the caller-supplied search keyword directly into a SQL statement with no escaping and no parameter binding. 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 resulting statement runs on a read-write SQLite handle through a driver that executes stacked (;-separated) statements, against the global blocks table spanning all cleartext notebooks. An unauthenticated request can therefore read and write database content across every non-encrypted notebook on the instance. Details Data flow, unescaped and unbound at every hop: - searchDocs (kernel/api/filetree.go): k := arg["k"].(string) passed straight to model.SearchDocs(k, …), no sanitization. - SearchDocs (kernel/model/file.go): after TrimSpace and strings.Fields, each token is spliced into a single-quoted LIKE literal by concatenation condition.WriteString("(hpath LIKE '%" + k +…

Published by the source

1 Oct 2026, 14:38 UTC

Last modified by the source

7 Oct 2026, 17:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-33jq-p8c2-q3q4

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6621

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-33jq-p8c2-q3q4

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

# Patch Next advisory brief: CVE-2026-69085

Advisory: SiYuan: Unauthenticated SQL injection in searchDocs via unescaped keyword (publish mode): cross-notebook read/write with statement stacking
IDs: CVE-2026-69085, GHSA-33jq-p8c2-q3q4
Record: https://patchnext.com/advisories/cve-2026-69085 (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-20260721043339-eef10568384e. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260721043339-eef10568384e; fixed in 0.0.0-20260721043339-eef10568384e

## 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/GO-2026-6621 (OSV record GO-2026-6621 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721043339-eef10568384e (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-33jq-p8c2-q3q4 (OSV record GHSA-33jq-p8c2-q3q4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721043339-eef10568384e (fixed))
- Verified: https://github.com/advisories/GHSA-33jq-p8c2-q3q4 (GitHub-reviewed advisory GHSA-33jq-p8c2-q3q4 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721043339-eef10568384e)

Commands are suggestions: review each one before running it.