Is CVE-2026-116170 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116170 being exploited in the wild.

How severe is CVE-2026-116170?

Medium severity, with a CVSS score of 4.9, published 25 October 2026.

Is there a fix for CVE-2026-116170?

Yes: fixed in v3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-116170 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-116170?

Check whether you run SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116170: SiYuan SQL injection in history search

CVE-2026-116170 · Severity: medium · CVSS 4.9 · Published 2026-10-25

SiYuan is an open-source note-taking application that maintains a searchable history database. An administrator with the API token can inject SQL commands via search parameters to exfiltrate deleted notes, including their content, titles, and file paths. This allows unauthorized disclosure of sensitive information that users intended to be permanently deleted.

Technologies: SiYuan. Vendors: SiYuan.

Quick answers

Is CVE-2026-116170 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116170 being exploited in the wild.
How severe is CVE-2026-116170?: Medium severity, with a CVSS score of 4.9, published 25 October 2026.
Which products and versions are affected?: SiYuan before 3.8.7.
Is there a fix for CVE-2026-116170?: Yes: fixed in v3.8.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116170 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-116170?: Check whether you run SiYuan at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: v3.8.7

Technical details

The history search endpoints in kernel/model/history.go concatenate the `op` and `query` parameters directly into SQL WHERE clauses without escaping when `type=3` (DocID search), then execute the result against history.db via raw SQL sinks with no validation. An authenticated admin (API token holder) can send UNION SELECT payloads to /api/history/searchHistory or /api/history/getHistoryItems to bypass filters and extract arbitrary history records.

Affected products

SiYuan SiYuan before 3.8.7

Timeline

2026-10-09: disclosed
2026-10-25: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.