SiYuan: Cross-boundary metadata disclosure via getBlockInfo (publish mode): reader-reachable document title/root info for publish-forbidden docs; sibling getDocInfo is filtered

Exploitation

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

CVSS

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

EPSS

• CVE-2026-68585: 0.24% estimated exploitation activity in the next 30 days; percentile 15.61 (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-68585. Summary The /api/block/getBlockInfo endpoint returns document root metadata including the document title (rootTitle) for a block in a publish-forbidden document, with no publish-access check. Its sibling /api/block/getDocInfo applies the publish-access filter, getBlockInfo does not. Both are gated by CheckAuth only, so getBlockInfo is reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. Details The list/info side of this API is filtered while the block-info twin is not the asymmetry indicates an oversight rather than intended behavior: | Endpoint | Returns | Publish-access filter | Route | |---|---|---|---| | getDocInfo | document info/metadata | present | CheckAuth | | getBlockInfo | box, path, rootID, rootTitle, rootChildID, rootIcon | none | CheckAuth | getBlockInfo takes a caller-supplied block ID, validates only its format, and returns the containing document's root…

Published by the source

3 Sep 2026, 21:22 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-pm3w-vxp9-ccwc

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6384

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pm3w-vxp9-ccwc

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

# Patch Next advisory brief: CVE-2026-68585

Advisory: SiYuan: Cross-boundary metadata disclosure via getBlockInfo (publish mode): reader-reachable document title/root info for publish-forbidden docs; sibling getDocInfo is filtered
IDs: CVE-2026-68585, GHSA-pm3w-vxp9-ccwc
Record: https://patchnext.com/advisories/cve-2026-68585 (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: Medium (CVSS 5.8)
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-20260721014951-ffde3b21eca4. A vendor fix does not mean a deployment is fixed.

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

## 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-pm3w-vxp9-ccwc (OSV record GHSA-pm3w-vxp9-ccwc lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721014951-ffde3b21eca4 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6384 (OSV record GO-2026-6384 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721014951-ffde3b21eca4 (fixed))
- Verified: https://github.com/advisories/GHSA-pm3w-vxp9-ccwc (GitHub-reviewed advisory GHSA-pm3w-vxp9-ccwc lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721014951-ffde3b21eca4)

Commands are suggestions: review each one before running it.