SiYuan: SQL injection in backlink/mention search via unescaped stored and client input (publish mode): first-order (client keyword) and second-order (stored document title) breakout on read-write…

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-72811: 0.44% estimated exploitation activity in the next 30 days; percentile 37.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CVE: This vulnerability corresponds to CVE-2026-72811. Summary The backlink/mention search query (kernel/model/backlink.go) concatenates stored block metadata (title, name, alias, anchor text) and the client-supplied keyword into a SQL MATCH/search statement, escaping only the double-quote character (") and not the single quote ('). A single quote in either the client keyword or in stored document metadata breaks out of the string literal. The query runs on the main read-write siyuan.db handle through a statement-stacking-capable driver. This yields two vectors: - First-order: a client-supplied keyword containing ' injects directly. This path is reachable by an anonymous reader on the publish surface. - Second-order: a document whose title/name/alias contains ' is stored safely (indexing uses parameterized inserts) but detonates when that stored value is later concatenated into the backlink query including on another user's kernel that has ingested the malicious document. Details…

Published by the source

3 Sep 2026, 22:27 UTC

Last modified by the source

10 Sep 2026, 15:15 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-q2vg-7qgx-x5fc

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6402

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-q2vg-7qgx-x5fc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-72811

Advisory: SiYuan: SQL injection in backlink/mention search via unescaped stored and client input (publish mode): first-order (client keyword) and second-order (stored document title) breakout on read-write…
IDs: CVE-2026-72811, GHSA-q2vg-7qgx-x5fc
Record: https://patchnext.com/advisories/cve-2026-72811 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/siyuan-note/siyuan/kernel 0.0.0-20260723004839-1a5b3431d5ab. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260723004839-1a5b3431d5ab; fixed in 0.0.0-20260723004839-1a5b3431d5ab

## Suggested inspection (read-only)
- Go github.com/siyuan-note/siyuan/kernel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/siyuan-note/siyuan/kernel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q2vg-7qgx-x5fc (OSV record GHSA-q2vg-7qgx-x5fc lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260723004839-1a5b3431d5ab (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6402 (OSV record GO-2026-6402 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260723004839-1a5b3431d5ab (fixed))
- Verified: https://github.com/advisories/GHSA-q2vg-7qgx-x5fc (GitHub-reviewed advisory GHSA-q2vg-7qgx-x5fc lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260723004839-1a5b3431d5ab)

Commands are suggestions: review each one before running it.