# 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 Advisory record · `GHSA-v684-q882-jgmq` - **Identifiers:** `GHSA-v684-q882-jgmq` · `CVE-2026-72789` · `GO-2026-6434` - **State:** Confirmed - **Severity:** CVSS 9.2 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 8 Sept 2026 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 8 Sept 2026, 17:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.2: 9.0 or more. How we decide what’s critical: ## Affected packages - `github.com/siyuan-note/siyuan/kernel` (Go): affected `<0.0.0-20260726020813-a25c2dd06aae`; fixed in `0.0.0-20260726020813-a25c2dd06aae` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > SiYuan's kernel (Go package github.com/siyuan-note/siyuan/kernel) before 0.0.0-20260726020813-a25c2dd06aae lets anonymous publish-mode readers list encrypted notebooks and retrieve their fully decrypted document content while the notebook is unlocked, because the publish access check defaults to allowing any notebook not explicitly listed. An attacker needs only publish-mode access, with no password or key material; the exposure lasts while the legitimate user has the notebook open. Upgrade to 0.0.0-20260726020813-a25c2dd06aae or later. No workaround is listed. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.2 Critical, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0037, the 31st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-v684-q882-jgmq) ## Sources - [GitHub Advisory Database: GHSA-v684-q882-jgmq](https://github.com/advisories/GHSA-v684-q882-jgmq) - [OSV: GHSA-v684-q882-jgmq](https://osv.dev/vulnerability/GHSA-v684-q882-jgmq) - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .