CVE-2026-69083: github.com/siyuan-note/siyuan/kernel (Go)

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
EPSS 0.5%, percentile 40: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 40% of all scored CVEs (low). EPSS is a probability, not a verdict.
Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
Only applies if your dependency tree includes github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260721004815-cf42dd5680c8, fixed in 0.0.0-20260721004815-cf42dd5680c8. Check your lockfile, including transitive dependencies.

What it is

SiYuan versions before v3.7.3 contain SQL injection vulnerabilities in the fullTextSearchAssetContent endpoint reachable by unauthenticated users and publish RoleReader tokens. Attackers can execute arbitrary SQL on the read-write asset-content database via unescaped method parameters and REGEXP clauses to read, modify, or delete cross-notebook data.

From the GitHub advisory

CVE: This vulnerability corresponds to CVE-2026-69083.

Summary

The /api/search/fullTextSearchAssetContent endpoint exposes two SQL flaws on the asset-content database, both reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false:

1. method 2 passes a client-supplied SQL statement to the read-write asset-content DB with no single-statement or read-only guard, and without the admin restriction its sibling fullTextSearchBlock applies to the same SQL method. 2. method 3 builds a REGEXP clause by concatenating the client expression with no quote-escaping, permitting SQL breakout while the equivalent block-search builder does escape.

Both run on a read-write handle through a statement-stacking-capable driver, spanning the cross-notebook asset-content store.

Weakness type: CWE-89.

Product: github.com/siyuan-note/siyuan/kernel (Go) · Assigned by: VulnCheck · Published: 2026-08-03

Affected and fixed versions

Ecosystem	Package	Vulnerable	First fixed
Go	`github.com/siyuan-note/siyuan/kernel`	< 0.0.0-20260721004815-cf42dd5680c8	0.0.0-20260721004815-cf42dd5680c8

Vendor	Product	Affected versions (per CVE record)
siyuan-note	siyuan	< 3.7.3

Severity scores

Scored by	CVSS	Score	Vector
VulnCheck	4.0	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`
VulnCheck	3.1	10 Critical	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`
GitHub	3.1	10.0	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`

Attack vector: network (remotely reachable)
Attack complexity: low
Attack requirements: none
Privileges required: none (no login)
User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
FIRST EPSS (model of 2026-10-21): 0.47% probability of exploitation activity in the next 30 days; percentile 40.

Timeline

2026-08-03 — CVE record published by VulnCheck
2026-08-14 — CVE record last updated
2026-09-03 — GitHub-reviewed advisory GHSA-fph3-ghq9-vw66 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.