Which versions of SiYuan are affected by CVE-2026-69085?

SiYuan versions before 3.7.3 contain a critical SQL injection vulnerability (CVE-2026-69085, CVSS 9.9) allowing unauthenticated attackers to read and modify all notebook content when authentication…. A patch is available.

How to fix or mitigate CVE-2026-69085?

Within 24 hours, identify all SiYuan instances in your environment and document their current versions and authentication configuration, specifically whether Publish.Auth.Enable is enabled. Within 7 days, upgrade all affected instances to v3.7.3 or later and verify authentication controls are properly configured. Within 30 days, conduct a full audit of notebook access and modification logs during the vulnerability exposure period to detect any signs of unauthorized access or tampering.

SiYuan CVE-2026-69085

Q: What is the CVSS score of CVE-2026-69085?

CVE-2026-69085 has a CVSS 4.0 base score of 9.9 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-52278 CRITICAL

SQL Injection (CWE-89)

2026-08-03 VulnCheck

GHSA-5w4j-hchp-r332

SQLi Siyuan Siyuan Note

9.9

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

9.9 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

9.1 CRITICAL

Unauthenticated in the publish/Publish.Auth.Enable=false configuration justifies PR:N and AC:L; stacked read-write SQL gives C:H/I:H, with no availability impact so A:N and scope unchanged within the app's own database.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 03, 2026 - 14:26 vuln.today

Patch available

Aug 03, 2026 - 14:02 EUVD

CVE Published

Aug 03, 2026 - 13:20 cve.org

CRITICAL 9.9

DescriptionCVE.org

SiYuan before v3.7.3 contains a SQL injection vulnerability in the /api/filetree/searchDocs endpoint, where the caller-supplied keyword parameter is concatenated directly into SQL statements with no escaping or parameter binding. The endpoint is reachable by a publish RoleReader token, or unauthenticated when publish mode is enabled with Publish.Auth.Enable set to false. Because the statement executes on a read-write SQLite handle via a driver that supports stacked (semicolon-separated) statements, an attacker can read and modify database content across all cleartext (non-encrypted) notebooks on the instance.

AnalysisAI

SQL injection in SiYuan personal knowledge-management software (all versions before v3.7.3) lets attackers inject arbitrary SQL through the unescaped keyword parameter of the /api/filetree/searchDocs endpoint. Because the query runs on a read-write SQLite handle that permits stacked statements, an attacker can both read and tamper with content across every cleartext notebook, and the endpoint is reachable unauthenticated when publish mode runs with Publish.Auth.Enable=false. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis, and the CVSS 4.0 score is 9.9.

Technical ContextAI

SiYuan is a self-hosted block-based note-taking application that stores note content and metadata in a local SQLite database and exposes a Go-based HTTP API. The flaw is a classic CWE-89 SQL injection: the /api/filetree/searchDocs handler concatenates the caller-supplied keyword directly into SQL text with no parameter binding or escaping. The severity is amplified by two implementation details - the query executes against a read-write (not read-only) SQLite connection, and the database driver honors stacked, semicolon-separated statements - so a single injection point yields both data exfiltration (SELECT) and arbitrary data modification (INSERT/UPDATE/DELETE) rather than read-only disclosure. The single affected CPE is cpe:2.3:a:siyuan-note:siyuan:*:*:*:*:*:*:*:*.

RemediationAI

Vendor-released patch: upgrade to SiYuan v3.7.3 or later, which is the primary and complete fix per the vendor advisory at https://github.com/siyuan-note/siyuan/security/advisories/GHSA-33jq-p8c2-q3q4. If immediate patching is not possible, disable publish mode entirely, or if publish mode is required, ensure Publish.Auth.Enable is set to true so the /api/filetree/searchDocs endpoint cannot be reached unauthenticated - with the trade-off that legitimate anonymous readers will then need credentials. As a further compensating control, restrict network access to the SiYuan instance (bind to localhost or place behind an authenticating reverse proxy / VPN) and avoid exposing the publish endpoint to untrusted networks; note this does not stop an authenticated RoleReader token holder from exploiting the flaw, so patching remains necessary. Encrypting notebooks reduces exposure of their contents but does not remediate the injection itself.