SiYuan: Publish-access filter on renderAttributeView leaves related-database content unfiltered and fails open on non-block first columns

Exploitation

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

CVSS

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

EPSS

• CVE-2026-72798: 0.43% estimated exploitation activity in the next 30 days; percentile 37.77 (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-72798. Summary renderAttributeView correctly applies the reader publish-access filter, but the filter's row-accessibility decision is keyed solely to the row's first cell, and it never inspects the remaining cells' values. Relation and Rollup cells carry mirrored content from a different database, so a row belonging to a published database can hand an anonymous reader the contents of a related database whose host document is hidden, publish-forbidden, or password-protected. Separately, when the first column is not a block value the accessibility check is skipped entirely and the row is returned unchecked. Note: This is distinct from the previously reported password-tier omission in the same function that concerns the row's own primary block, whereas these two defects concern (a) other cells' related-database content, which no row-level check covers and (b) rows where the first cell is not a block at all. A fix to the row-drop condition…

Published by the source

4 Sep 2026, 20: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-mfrj-v65r-979c

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6415

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mfrj-v65r-979c

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

# Patch Next advisory brief: CVE-2026-72798

Advisory: SiYuan: Publish-access filter on renderAttributeView leaves related-database content unfiltered and fails open on non-block first columns
IDs: CVE-2026-72798, GHSA-mfrj-v65r-979c
Record: https://patchnext.com/advisories/cve-2026-72798 (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: High (CVSS 8.6)
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-20260724121519-426991d155c0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260724121519-426991d155c0; fixed in 0.0.0-20260724121519-426991d155c0

## 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-mfrj-v65r-979c (OSV record GHSA-mfrj-v65r-979c lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724121519-426991d155c0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6415 (OSV record GO-2026-6415 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724121519-426991d155c0 (fixed))
- Verified: https://github.com/advisories/GHSA-mfrj-v65r-979c (GitHub-reviewed advisory GHSA-mfrj-v65r-979c lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724121519-426991d155c0)

Commands are suggestions: review each one before running it.