CVE-2026-32767: siyuan · SQL Injection
Affects siyuanSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.6.1 as a priority.
Data as of 1 Nov 2026, 08:20 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.6.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 31 Oct 2026.
What to do
Upgrade siyuan and siyuan-note/siyuan to 3.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| siyuan-notesiyuan | Affected
| Fixed in
|
GitHubsiyuan-note/siyuanpkg:github/siyuan-note/siyuanOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2026-32767, organizations should immediately upgrade SiYuan to version 3.6.1 or later, where the vulnerability has been fixed by enforcing proper authorization and read-only checks on the /api/search/fullTextSearchBlock endpoint. Until upgrading is possible, organizations should restrict access to the application to trusted users only and consider disabling or restricting the vulnerable endpoint if feasible. Implement network-level access controls such as IP whitelisting or VPN requirements to limit exposure. Conduct thorough audits of user roles and permissions to ensure that only necessary users have authenticated access, minimizing the attack surface. Monitor application logs for unusual SQL queries or unexpected database activity that could indicate exploitation attempts. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting the vulnerable endpoint. Regularly review and update security policies to enforce least privilege principles and ensure timely patch management for all software components.
Description
SiYuan is a personal knowledge management system. Versions 3.6.0 and below contain an authorization bypass vulnerability in the /api/search/fullTextSearchBlock endpoint. When the method parameter is set to 2, the endpoint passes user-supplied input directly as a raw SQL statement to the underlying SQLite database without any authorization or read-only checks. This allows any authenticated user — including those with the Reader role — to execute arbitrary SQL statements (SELECT, DELETE, UPDATE, DROP TABLE, etc.) against the application's database. This is inconsistent with the application's own security model: the dedicated SQL endpoint (/api/query/sql) correctly requires both CheckAdminRole and CheckReadonly middleware, but the search endpoint bypasses these controls entirely. This issue has been fixed in version 3.6.1.
References
- github.com/siyuan-note/siyuan/security/advisories/GHSA-j7wh-x834-p3r7 (opens in a new tab)
- github.com/siyuan-note/siyuan/issues/17209 (opens in a new tab)
- github.com/siyuan-note/siyuan/commit/d5e2d0bce0dffef5f61bd8066954bc2d41181fc5 (opens in a new tab)
- github.com/siyuan-note/siyuan/releases/tag/v3.6.1 (opens in a new tab)