Skip to content

← Actionable
High, CVSS 7.5amended

SiYuan: SQL Query in Block Search Exposes Hidden Published Document Content

CVE-2026-59834GHSA-h89q-4j2h-7h88

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/siyuan-note/siyuan/kernel 0.0.0-20260704035518-d0f0fe146fb0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-59834: 0.48% estimated exploitation activity in the next 30 days; percentile 41.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Siyuan's block search endpoint concatenates attacker-controlled paths[] values into SQL predicates used by non-SQL search modes. Through Siyuan's publish service, an unauthenticated visitor is forwarded to the kernel with a reader-role token and can reach POST /api/search/fullTextSearchBlock. An attacker can inject a UNION SELECT through paths[] and return rows from hidden documents while projecting an allowed visible box and path. The post-query publish access filter trusts the projected box and path, so the injected hidden row is returned to the publish visitor. Affected Code The API blocks explicit SQL search mode for non-admin users, but allows other search methods to use caller-controlled paths: Source: input/siyuan/kernel/api/search.go paths[] is parsed into notebook IDs and paths without SQL escaping or validation: Source: input/siyuan/kernel/api/search.go Those values are then concatenated directly into SQL: Source: input/siyuan/kernel/model/search.go Regexp search…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-h89q-4j2h-7h88

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6353

  3. Revision 1 · created ·

    Published from osv record GHSA-h89q-4j2h-7h88

Agent brief

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

# Patch Next advisory brief: CVE-2026-59834

Advisory: SiYuan: SQL Query in Block Search Exposes Hidden Published Document Content
IDs: CVE-2026-59834, GHSA-h89q-4j2h-7h88
Record: https://patchnext.com/advisories/cve-2026-59834 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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-20260704035518-d0f0fe146fb0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260704035518-d0f0fe146fb0; fixed in 0.0.0-20260704035518-d0f0fe146fb0

## 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-h89q-4j2h-7h88 (OSV record GHSA-h89q-4j2h-7h88 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260704035518-d0f0fe146fb0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6353 (OSV record GO-2026-6353 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260704035518-d0f0fe146fb0 (fixed))
- Verified: https://github.com/advisories/GHSA-h89q-4j2h-7h88 (GitHub-reviewed advisory GHSA-h89q-4j2h-7h88 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260704035518-d0f0fe146fb0)

Commands are suggestions: review each one before running it.

Loading voting…