SiYuan: Missing publish-access filter on getBlockAttrs and batchGetBlockAttrs discloses block attributes (name, alias, memo, custom fields) of protected documents

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-72803: 0.30% estimated exploitation activity in the next 30 days; percentile 22.35 (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-72803. Summary POST /api/attr/getBlockAttrs and POST /api/attr/batchGetBlockAttrs return a block's full attribute set (IAL) with no publish-access check. Both are CheckAuth-only, so they are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. An anonymous reader supplying a block ID receives the block's name, alias, memo, bookmark, tags, and every custom- attribute including for blocks in publish-forbidden and password-protected documents. The batch variant accepts an ID list, making it a bulk extraction primitive. Details Neither handler applies a filter: sql.GetBlockAttrs is a direct database read returning the block's entire IAL: name, alias, memo, bookmark, tags, and any custom- key/value the user has set. Several of these are user-authored free text memos in particular are freeform notes attached to a block so this is document content, not merely structural metadata.…

Published by the source

3 Sep 2026, 22:58 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-qvq9-hq6p-v378

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6404

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qvq9-hq6p-v378

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

# Patch Next advisory brief: CVE-2026-72803

Advisory: SiYuan: Missing publish-access filter on getBlockAttrs and batchGetBlockAttrs discloses block attributes (name, alias, memo, custom fields) of protected documents
IDs: CVE-2026-72803, GHSA-qvq9-hq6p-v378
Record: https://patchnext.com/advisories/cve-2026-72803 (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-20260724093256-229fdffd7e4a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260724093256-229fdffd7e4a; fixed in 0.0.0-20260724093256-229fdffd7e4a

## 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-qvq9-hq6p-v378 (OSV record GHSA-qvq9-hq6p-v378 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724093256-229fdffd7e4a (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6404 (OSV record GO-2026-6404 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724093256-229fdffd7e4a (fixed))
- Verified: https://github.com/advisories/GHSA-qvq9-hq6p-v378 (GitHub-reviewed advisory GHSA-qvq9-hq6p-v378 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724093256-229fdffd7e4a)

Commands are suggestions: review each one before running it.