SiYuan: The publish-access gate treats encrypted notebooks as publicly accessible by default, allowing anonymous readers to retrieve fully decrypted document content while a notebook is unlocked

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-72789: 0.37% estimated exploitation activity in the next 30 days; percentile 30.82 (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-72789. Summary publishAccess.json is an opt-out list. The publish gate returns accessible for anything not explicitly listed in it. Encrypted notebooks are never written into that file, because only the administrator-gated setPublishAccess writes it and no part of the encryption subsystem does. Consequently every encrypted notebook is publish-accessible as far as the gate is concerned. While an encrypted notebook is unlocked, an anonymous reader in publish mode can list it, enumerate its documents, and retrieve their fully decrypted content. No key material, no password, and no cracking is involved. The kernel decrypts the data and serves it because the authorization layer never asks whether the notebook is encrypted. This is reported as a defect in the gate rather than in any individual handler. Endpoints that were previously reviewed and found to apply the correct checks do apply them. The checks return true. Details The gate defaults…

Published by the source

8 Sep 2026, 17:56 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-v684-q882-jgmq

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6434

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v684-q882-jgmq

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

# Patch Next advisory brief: CVE-2026-72789

Advisory: SiYuan: The publish-access gate treats encrypted notebooks as publicly accessible by default, allowing anonymous readers to retrieve fully decrypted document content while a notebook is unlocked
IDs: CVE-2026-72789, GHSA-v684-q882-jgmq
Record: https://patchnext.com/advisories/cve-2026-72789 (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-20260726020813-a25c2dd06aae. A vendor fix does not mean a deployment is fixed.

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

## 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-v684-q882-jgmq (OSV record GHSA-v684-q882-jgmq lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726020813-a25c2dd06aae (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6434 (OSV record GO-2026-6434 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726020813-a25c2dd06aae (fixed))
- Verified: https://github.com/advisories/GHSA-v684-q882-jgmq (GitHub-reviewed advisory GHSA-v684-q882-jgmq lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260726020813-a25c2dd06aae)

Commands are suggestions: review each one before running it.