# CVE-2026-69085: SiYuan before v3.7.3 SQL Injection via searchDocs

> An attacker can execute arbitrary SQL commands via the searchDocs endpoint to read and modify database content in SiYuan.

- **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-33jq-p8c2-q3q4, GO-2026-6621

## What is CVE-2026-69085?

CVE-2026-69085 is a critical SQL injection vulnerability in siyuan-note siyuan, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan before v3.7.3 contains a SQL injection vulnerability in the /api/filetree/searchDocs endpoint, where the caller-supplied keyword parameter is concatenated directly into SQL statements with no escaping or parameter binding. The endpoint is reachable by a publish RoleReader token, or unauthenticated when publish mode is enabled with Publish.Auth.Enable set to false. Because the statement executes on a read-write SQLite handle via a driver that supports stacked (semicolon-separated) statements, an attacker can read and modify database content across all cleartext (non-encrypted) notebooks on the instance.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-69085?

3 open source packages ship an affected version, including github.com/siyuan-note/siyuan/kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260721043339-eef10568384e |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260721043339-eef10568384e |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260721043339-eef10568384e |

## How do I fix CVE-2026-69085?

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260721043339-eef10568384e or later.

## Is CVE-2026-69085 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69085 exists.

Public exploit code:

- SiYuan <=3.7.2 - SQL Injection (nuclei): http/cves/2026/CVE-2026-69085.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-69085 and fix it if it is affected.

What it is: CVE-2026-69085 is a critical SQL injection vulnerability in siyuan-note siyuan, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-69085 exists.

Affected packages and fixed versions:
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260721043339-eef10568384e
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260721043339-eef10568384e
- github.com/siyuan-note/siyuan/kernel (Go): affected all versions; fixed in 0.0.0-20260721043339-eef10568384e

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-69085/ (Markdown: https://insights.sbomify.com/CVE-2026-69085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-69085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-69085
- OSV: https://osv.dev/vulnerability/CVE-2026-69085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-69085/
Summaries are generated and may contain mistakes; the official description above is the record.