SiYuan: getEncryptedNotebookStatus discloses names and current lock/unlock state of all encrypted notebooks to anonymous readers

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-72797: 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-72797. Summary POST /api/notebook/getEncryptedNotebookStatus returns the identifier, name, and current lock state of every encrypted notebook, with no publish-access filtering. The route is registered CheckAuth only, no CheckReadonly, no CheckAdminRole so it is reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false. Encrypted notebooks are private by design; their names frequently reveal the sensitive topic that motivated encrypting them. Details Route registration (kernel/api/router.go:131): The handler (kernel/api/notebook.go) accepts no arguments and contains no IsReadOnlyRoleContext branch and no publish-access filter of any kind. It returns, for every encrypted notebook, {id, name, unlocked}, the notebook's box.Name and its live lock state together with enabled, count, migrationPending, migrationBoxes, and hasHistoryDependency. Guarded-sibling asymmetry. The primary notebook listing…

Published by the source

4 Sep 2026, 21:01 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-f2rw-w22v-54vh

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6414

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f2rw-w22v-54vh

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

# Patch Next advisory brief: CVE-2026-72797

Advisory: SiYuan: getEncryptedNotebookStatus discloses names and current lock/unlock state of all encrypted notebooks to anonymous readers
IDs: CVE-2026-72797, GHSA-f2rw-w22v-54vh
Record: https://patchnext.com/advisories/cve-2026-72797 (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-20260724123622-8fb1b5766093. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260724123622-8fb1b5766093; fixed in 0.0.0-20260724123622-8fb1b5766093

## 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-f2rw-w22v-54vh (OSV record GHSA-f2rw-w22v-54vh lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724123622-8fb1b5766093 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6414 (OSV record GO-2026-6414 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724123622-8fb1b5766093 (fixed))
- Verified: https://github.com/advisories/GHSA-f2rw-w22v-54vh (GitHub-reviewed advisory GHSA-f2rw-w22v-54vh lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260724123622-8fb1b5766093)

Commands are suggestions: review each one before running it.