Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Critical severity, with a CVSS score of 10, published 3 August 2026.
- Which products and versions are affected?
- github.com/siyuan-note/siyuan (Go) < 3.7.3; SiYuan < 3.7.3.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a web application.
- Am I affected?
- Check whether you run github.com/siyuan-note/siyuan (Go) or 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.
Technical details
The vulnerability exists in the /api/search/fullTextSearchAssetContent endpoint and comprises two distinct SQL injection flaws. Method 2 passes client-supplied SQL statements directly to the asset-content database without single-statement or read-only guards and lacks the admin-role checks present in the sibling fullTextSearchBlock endpoint. Method 3 constructs REGEXP clauses by concatenating user input without quote escaping, allowing SQL injection breakout (whereas the equivalent block-search builder properly escapes quotes). Both execute on a read-write database handle through a stacking-capable SQLite driver with cross-notebook scope. The endpoint's CheckAuth-only route protection allows unauthenticated users and publish RoleReader tokens to reach the vulnerable code. No patches are available as of the advisory publication, though version 3.7.3 is referenced as the fixed version in some references.
Affected products
- SiYuan SiYuan < 3.7.3
Timeline
- 2026-08-03: disclosed
- 2026-08-03: advisory
- 2026-09-03: other: Advisory withdrawn as duplicate of GHSA-fph3-ghq9-vw66