Skip to main content
CVE-2026-116170VulnerabilityPublished 10/25/2026

CVE-2026-116170: siyuan · SQL Injection

Affects siyuan-note siyuanSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium · fixed in 3.8.7 : update siyuan-note siyuan when convenient.

Data as of 10/25/2026, 16:50:55 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.8.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
siyuan-notesiyuanAffected
  • <3.8.7
Fixed in
  • 3.8.7
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threatsAffected
  • <3.8.7
Fixed in
  • 3.8.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in SiYuan version 3.8.7 and later. Users should upgrade to version 3.8.7 or newer to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

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.

Impact

An attacker with admin-token privileges can exploit this vulnerability to perform SQL injection attacks that disclose sensitive historical data stored in the history.db database. This includes deleted document contents, titles, and file paths, potentially leading to unauthorized data exposure.

References

Community reviews

Loading reviews…