CVE-2026-87808: Protection Mechanism Failure in siyuan-note siyuan
SiYuan versions <= 3.8.1 contain an incomplete fix for CVE-2026-32767 (GHSA-j7wh-x834-p3r7). The prior fix (commit d5e2d0bc) added an administrator check for SQL mode (method=2) in POST /api/search/fullTextSearchBlock, but the endpoint still does not enforce the application's read-only boundary: for method=2 it forwards caller-supplied SQL to the blocks database query path without calling model.CheckReadonly or CheckReadonlyStatementInBox. As a result, when a workspace runs in read-only mode (--readonly=true), an authenticated administrator can submit arbitrary SQL through /api/search/fullTextSearchBlock and obtain raw read access to the blocks database, even though the dedicated /api/query/sql endpoint is blocked in that mode. Fixed in v3.8.2.
AI Analysis
Technical Summary
CVE-2026-87808 describes a protection mechanism failure in SiYuan note-taking software versions <= 3.8.1. The vulnerability stems from an incomplete fix for CVE-2026-32767, where the /api/search/fullTextSearchBlock endpoint allows an authenticated administrator to submit arbitrary SQL queries when the workspace is in read-only mode (--readonly=true). The endpoint forwards caller-supplied SQL to the blocks database query path without enforcing read-only checks (model.CheckReadonly or CheckReadonlyStatementInBox), enabling unauthorized raw read access. The dedicated /api/query/sql endpoint is correctly blocked in read-only mode, but this endpoint is not. The flaw is resolved in version 3.8.2.
Potential Impact
An authenticated administrator can bypass the read-only mode restriction and execute arbitrary SQL queries on the blocks database, potentially exposing sensitive data. This undermines the intended read-only protection of the workspace, allowing unauthorized data access despite the read-only configuration. The vulnerability does not require user interaction and has a network attack vector with low complexity, making it a high-severity issue.
Mitigation Recommendations
Upgrade to SiYuan version 3.8.2 or later, where this vulnerability is fixed. The fix properly enforces read-only boundaries on the /api/search/fullTextSearchBlock endpoint, preventing arbitrary SQL execution in read-only mode. Until upgrading, restrict administrator access and avoid running workspaces in read-only mode if possible.
CVE-2026-87808: Protection Mechanism Failure in siyuan-note siyuan
Description
SiYuan versions <= 3.8.1 contain an incomplete fix for CVE-2026-32767 (GHSA-j7wh-x834-p3r7). The prior fix (commit d5e2d0bc) added an administrator check for SQL mode (method=2) in POST /api/search/fullTextSearchBlock, but the endpoint still does not enforce the application's read-only boundary: for method=2 it forwards caller-supplied SQL to the blocks database query path without calling model.CheckReadonly or CheckReadonlyStatementInBox. As a result, when a workspace runs in read-only mode (--readonly=true), an authenticated administrator can submit arbitrary SQL through /api/search/fullTextSearchBlock and obtain raw read access to the blocks database, even though the dedicated /api/query/sql endpoint is blocked in that mode. Fixed in v3.8.2.
CVSS v4.0
Score 8.7high
Affected software
pkg:github/siyuan-note/siyuanRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-87808 describes a protection mechanism failure in SiYuan note-taking software versions <= 3.8.1. The vulnerability stems from an incomplete fix for CVE-2026-32767, where the /api/search/fullTextSearchBlock endpoint allows an authenticated administrator to submit arbitrary SQL queries when the workspace is in read-only mode (--readonly=true). The endpoint forwards caller-supplied SQL to the blocks database query path without enforcing read-only checks (model.CheckReadonly or CheckReadonlyStatementInBox), enabling unauthorized raw read access. The dedicated /api/query/sql endpoint is correctly blocked in read-only mode, but this endpoint is not. The flaw is resolved in version 3.8.2.
Potential Impact
An authenticated administrator can bypass the read-only mode restriction and execute arbitrary SQL queries on the blocks database, potentially exposing sensitive data. This undermines the intended read-only protection of the workspace, allowing unauthorized data access despite the read-only configuration. The vulnerability does not require user interaction and has a network attack vector with low complexity, making it a high-severity issue.
Mitigation Recommendations
Upgrade to SiYuan version 3.8.2 or later, where this vulnerability is fixed. The fix properly enforces read-only boundaries on the /api/search/fullTextSearchBlock endpoint, preventing arbitrary SQL execution in read-only mode. Until upgrading, restrict administrator access and avoid running workspaces in read-only mode if possible.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-09T10:30:15.669Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa14507acd9273b49403550
Added to database: 09/09/2026, 11:37:43 UTC
Last enriched: 09/09/2026, 11:52:58 UTC
Last updated: 09/09/2026, 21:36:32 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.