SiYuan: The reference filter for getRefIDs checks visibility but not the password tier, disclosing that password-protected documents reference a given block

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-73606: 0.33% estimated exploitation activity in the next 30 days; percentile 25.60 (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.

Summary /api/block/getRefIDs filters its results for reader roles through a helper that checks only the visibility tiers. The password tier is not checked, because the helper does not receive the request context and therefore cannot evaluate the publish auth cookie. A reader who has not entered a document's publish password learns that the document references a given block. A function ten lines away in the same file does perform the full check, on the same input type. Details Route, identical at eef105683 (kernel/api/router.go:235) and dev a7ae96ce (:245): No CheckReadonly, no CheckAdminRole. The filter chain. getRefIDs (kernel/api/block.go:631) checks isEncryptedNotebookDeniedForPublish, calls model.GetBlockRefsInBox, then for read-only roles: FilterRefDefsByPublishIgnore (kernel/model/publishaccess.go:1324) collects the reference and definition identifiers, resolves their block trees, and delegates the decision to FilterBlockTreesByPublishIgnore (:1314), whose entire body is:…

Published by the source

1 Oct 2026, 16:29 UTC

Last modified by the source

7 Oct 2026, 17:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-vg99-7gj7-2fr5

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6635

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-vg99-7gj7-2fr5

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

# Patch Next advisory brief: CVE-2026-73606

Advisory: SiYuan: The reference filter for getRefIDs checks visibility but not the password tier, disclosing that password-protected documents reference a given block
IDs: CVE-2026-73606, GHSA-vg99-7gj7-2fr5
Record: https://patchnext.com/advisories/cve-2026-73606 (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-20260812083335-251596fc0de2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260812083335-251596fc0de2; fixed in 0.0.0-20260812083335-251596fc0de2

## 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/GO-2026-6635 (OSV record GO-2026-6635 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-vg99-7gj7-2fr5 (OSV record GHSA-vg99-7gj7-2fr5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://github.com/advisories/GHSA-vg99-7gj7-2fr5 (GitHub-reviewed advisory GHSA-vg99-7gj7-2fr5 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2)

Commands are suggestions: review each one before running it.