# CVE-2026-72807: SiYuan before v3.7.4 SQL Injection via queryBlocks template

> Attackers can execute arbitrary SQL via malicious documents, enabling read and write access to notebooks in SiYuan.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Aug 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-x67c-8pwr-m8g3, GO-2026-6410

## What is CVE-2026-72807?

CVE-2026-72807 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SiYuan versions before v3.7.4 contain a second-order SQL injection vulnerability in attribute-view template columns that expose the queryBlocks function, which executes raw SQL using string substitution instead of parameterized queries. Attackers can distribute malicious SiYuan documents or packages with crafted template columns that execute arbitrary SQL on a victim's kernel when the package is imported and rendered, enabling read and write access across notebooks.

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

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

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

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

Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260723035036-0a176345e02a or later.

## Is CVE-2026-72807 being exploited?

There is no known exploitation of CVE-2026-72807 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72807 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 12 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-72807 in the wild and no public exploit code.

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

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

## Sources

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

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