# CVE-2026-59834: SiYuan: SQL Query in Block Search Exposes Hidden Published Document Content

> An unauthenticated attacker can inject SQL into the block search endpoint to read content from hidden documents in SiYuan.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-h89q-4j2h-7h88, GO-2026-6353

## What is CVE-2026-59834?

CVE-2026-59834 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SiYuan is an open-source personal knowledge management system. Prior to 3.7.1, the block search endpoint POST /api/search/fullTextSearchBlock concatenates attacker-controlled paths values into SQL predicates used by non-SQL search modes, allowing an unauthenticated publish visitor to inject a UNION SELECT and return rows from hidden documents by projecting an allowed visible box and path. This issue is fixed in versions 3.7.1.

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

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

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-20260704035518-d0f0fe146fb0 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260704035518-d0f0fe146fb0 |
| `github.com/siyuan-note/siyuan/kernel` | Go | All versions | 0.0.0-20260704035518-d0f0fe146fb0 |

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260704035518-d0f0fe146fb0 or later.

## Is CVE-2026-59834 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59834 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 9 Jul 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-59834 exists.

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

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-59834/ (Markdown: https://insights.sbomify.com/CVE-2026-59834/index.md)
```

## Sources

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

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