# CVE-2026-93591: SiYuan before 3.8.3 SQL Injection via unescaped tag in graph.go

> Attackers can inject SQL via graph endpoints to exfiltrate private data from SiYuan notebooks.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-4m3r-2vx9-4x56, GHSA-5rwv-4j4c-f954

## What is CVE-2026-93591?

CVE-2026-93591 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SiYuan versions before 3.8.3 contain an SQL injection vulnerability in the graph.go query2Stmt function where tag values are concatenated raw into SQL string literals without escaping single quotes. A publish-mode reader or anonymous visitor can inject SQL via inline HTML span tags in the getGraph endpoint to execute arbitrary queries on the read-write database and exfiltrate private data across notebooks.

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

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


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

No fix has been published for CVE-2026-93591 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93591 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93591 is a high-severity SQL injection vulnerability in siyuan-note siyuan, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93591 exists.

Affected product: siyuan-note siyuan. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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