CVE-2026-116170 SiYuan before v3.8.7 SQL Injection via History Search op and query
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-116170 and fix it if it is affected.
What it is: CVE-2026-116170 is a medium-severity vulnerability in siyuan-note siyuan, published on 25 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116170 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-116170/ (Markdown: https://insights.sbomify.com/CVE-2026-116170/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-116170?
CVE-2026-116170 is a medium-severity vulnerability in siyuan-note siyuan, published on 25 Oct 2026.
Official description
SiYuan before v3.8.7 contains an sql injection vulnerability that allows admin-token holders to read history.db by injecting unescaped op and type=3 query values. Attackers can send crafted UNION SELECT payloads to searchHistory or getHistoryItems endpoints to exfiltrate deleted document content, titles, and paths.
Weakness: CWE-89
Which versions are affected by CVE-2026-116170?
How do I fix CVE-2026-116170?
No fix has been published for CVE-2026-116170 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-116170 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116170 exists.
Sources
Also known as GHSA-4hjx-84f6-gr7c, GHSA-hf8g-c9wm-2xp9.