CVE-2026-73607: SiYuan Outline State For Any Document, Vulnerability

MODERATE
Advisory Identifier: GHSA-53fp-9jmv-227g
CVSS 5.8
CWE-862
Published
Advisory Summary

CVE-2026-73607 is a MODERATE (CVSS 5.8) outline state for any document, vulnerability (CWE-862: Missing Authorization) affecting SiYuan libraries in the Go ecosystem. The issue involves outline state for any document, including documents forbidden to readers, is returned by /api/storage/getoutlinestorage with no access check. Remediation is available by upgrading affected packages to version 0.0.0-20260812083335-251596fc0de2.

CVE-2026-73607 at a Glance

CVE Identifier CVE-2026-73607
GHSA Identifier GHSA-53fp-9jmv-227g
Severity MODERATE
CVSS v3.1 Base Score 5.8
CWE Classification CWE-862: Missing Authorization
Affected Product SiYuan
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-73607

To remediate this vulnerability, upgrade all affected SiYuan dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/siyuan-note/siyuan/kernel fixed: 0.0.0-20260812083335-251596fc0de2
Upgrade github.com/siyuan-note/siyuan/kernel to 0.0.0-20260812083335-251596fc0de2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/siyuan-note/siyuan/kernel

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-73607, inspect your project dependencies for SiYuan:

inspect dependencies for github.com/siyuan-note/siyuan/kernel

Analyze the terminal output to locate any version of SiYuan in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20260812083335-251596fc0de2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In SiYuan, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `/api/storage/getOutlineStorage` is registered with `CheckAuth` only and performs no authorization of any kind. Given a document identifier it returns that document's stored outline state, regardless of the document's publish tier. The two write endpoints for the same data, `setOutlineStorage` and `removeOutlineStorage`, both carry `CheckAdminRole` and `CheckReadonly`. Only the read path is unguarded. ### Details **Routes.** `kernel/api/router.go:103` on master, `:108` on the development branch: ```go ginServer.Handle("POST", "/api/storage/getOutlineStorage", model.CheckAuth, getOutlineStorage) ginServer.Handle("POST", "/api/storage/setOutlineStorage", model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, setOutlineStorage) ginServer.Handle("POST", "/api/storage/removeOutlineStorage", model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, removeOutlineStorage) ``` **Handler.** `kernel/api/storage.go:466` on the development branch, `:469` on master, identical. It binds `docID` and calls `model.GetOutlineStorage(docID)`, which iterates the stored outline documents and returns the entry whose `DocID` matches. There is no filter function on this path at all: no `*gin.Context`, no publish-access check, no password check, no visibility check. The caller supplies the identifier and receives the payload. **What is stored.** `type OutlineDoc { DocID string; Data map[string]any }`. The client writes it from `app/src/layout/dock/Outline.ts:742`: ```js fetchPost("/api/storage/setOutlineStorage", { docID: this.blockId, val: { expandIds: this.tree.getExpandIds() } }); ``` So the payload is the set of heading block identifiers the administrator has expanded in the outline pane for that document. Secondarily, an empty result versus a populated one indicates whether the administrator has ever worked with that document's outline. **Not covered by the local-storage fix.** Commit `4daee87d4` addressed `getLocalStorage`, `getLocalStorageVal`, `getLocalStorageVals` and `FilterLocalStorageByPublishAccess`. The word "outline" does not appear in that diff. That filter was under-inclusive; this endpoint has no filter to be under-inclusive. ### Proof of Concept Kernel 3.7.2, publish mode on port 6808, `Publish.Auth.Enable` false, anonymous client with no auth header. An administrator wrote outline state through the authenticated port: ``` POST /api/storage/setOutlineStorage {"docID":"<doc id>","val":{"openIDs":["<heading id>","<heading id>"]}} → {"code":0,"msg":"","data":null} ``` The same value read back anonymously: ``` POST http://127.0.0.1:6808/api/storage/getOutlineStorage {"docID":"<doc id>"} → {"code":0,"msg":"","data":{"openIDs":["<heading id>","<heading id>"]}} ``` With that document set to the forbidden tier, on the same anonymous session: | Endpoint | Result | |---|---| | `getDoc` (control) | `protyle-password--forbidden` placeholder, content withheld | | `getOutlineStorage` | full payload returned | The control establishes that the session is correctly denied the document itself. ### Impact An anonymous reader in publish mode, or any publish `RoleReader`, retrieves the administrator's outline state for any document whose identifier they hold, including documents in the forbidden tier that the publish filters otherwise withhold entirely. The disclosed values are heading block identifiers, usable as input to other endpoints, and the presence or absence of an entry indicates whether the administrator has worked with that document. No document text is returned. Confidentiality only. ### Suggested fix Gate the read path as the write paths already are. Either add `CheckAdminRole` and `CheckReadonly` at the route, matching `setOutlineStorage` and `removeOutlineStorage`, or pass `*gin.Context` into `GetOutlineStorage` and apply `checkBlockTreeAccessableByPublishAccess` against the requested `docID` before returning anything.

CVE-2026-73607 Affected SiYuan Versions

1 component(s)
Fixed Versions:
0.0.0-20260812083335-251596fc0de2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/siyuan-note/siyuan/kernel
Go
< 0.0.0-20260812083335-251596fc0de2
0.0.0-20260812083335-251596fc0de2

References

Frequently Asked Questions

What is CVE-2026-73607?
CVE-2026-73607 is a security vulnerability in SiYuan involving Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlineStorage with no access check under CWE-862: Missing Authorization.
Which SiYuan versions are affected?
Affected versions include releases prior to 0.0.0-20260812083335-251596fc0de2 across affected packages: github.com/siyuan-note/siyuan/kernel.
What version fixes CVE-2026-73607?
Upgrading to 0.0.0-20260812083335-251596fc0de2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/siyuan-note/siyuan/kernel affected?
Yes, github.com/siyuan-note/siyuan/kernel is affected in releases prior to 0.0.0-20260812083335-251596fc0de2. Upgrade your dependency to 0.0.0-20260812083335-251596fc0de2 or later.
What is the CVSS score of CVE-2026-73607?
CVE-2026-73607 has a CVSS v3.1 base score of 5.8 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N.
What CWE is associated with CVE-2026-73607?
CVE-2026-73607 is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2026-73607?
Run the dependency tree command: 'inspect dependencies for github.com/siyuan-note/siyuan/kernel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-53fp-9jmv-227g",
  "modified" : "2026-10-01T15:44:46Z",
  "published" : "2026-10-01T15:44:46Z",
  "aliases" : [ "CVE-2026-73607" ],
  "summary" : "SiYuan: Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlineStorage with no access check",
  "details" : "### Summary\n\n`/api/storage/getOutlineStorage` is registered with `CheckAuth` only and performs no authorization of any kind. Given a document identifier it returns that document's stored outline state, regardless of the document's publish tier.\n\nThe two write endpoints for the same data, `setOutlineStorage` and `removeOutlineStorage`, both carry `CheckAdminRole` and `CheckReadonly`. Only the read path is unguarded.\n\n### Details\n\n**Routes.** `kernel/api/router.go:103` on master, `:108` on the development branch:\n\n```go\nginServer.Handle(\"POST\", \"/api/storage/getOutlineStorage\",    model.CheckAuth, getOutlineStorage)\nginServer.Handle(\"POST\", \"/api/storage/setOutlineStorage\",    model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, setOutlineStorage)\nginServer.Handle(\"POST\", \"/api/storage/removeOutlineStorage\", model.CheckAuth, model.CheckAdminRole, model.CheckReadonly, removeOutlineStorage)\n```\n\n**Handler.** `kernel/api/storage.go:466` on the development branch, `:469` on master, identical. It binds `docID` and calls `model.GetOutlineStorage(docID)`, which iterates the stored outline documents and returns the entry whose `DocID` matches. There is no filter function on this path at all: no `*gin.Context`, no publish-access check, no password check, no visibility check. The caller supplies the identifier and receives the payload.\n\n**What is stored.** `type OutlineDoc { DocID string; Data map[string]any }`. The client writes it from `app/src/layout/dock/Outline.ts:742`:\n\n```js\nfetchPost(\"/api/storage/setOutlineStorage\", {\n    docID: this.blockId,\n    val: { expandIds: this.tree.getExpandIds() }\n});\n```\n\nSo the payload is the set of heading block identifiers the administrator has expanded in the outline pane for that document. Secondarily, an empty result versus a populated one indicates whether the administrator has ever worked with that document's outline.\n\n**Not covered by the local-storage fix.** Commit `4daee87d4` addressed `getLocalStorage`, `getLocalStorageVal`, `getLocalStorageVals` and `FilterLocalStorageByPublishAccess`. The word \"outline\" does not appear in that diff. That filter was under-inclusive; this endpoint has no filter to be under-inclusive.\n\n### Proof of Concept\n\nKernel 3.7.2, publish mode on port 6808, `Publish.Auth.Enable` false, anonymous client with no auth header.\n\nAn administrator wrote outline state through the authenticated port:\n\n```\nPOST /api/storage/setOutlineStorage\n{\"docID\":\"<doc id>\",\"val\":{\"openIDs\":[\"<heading id>\",\"<heading id>\"]}}\n→ {\"code\":0,\"msg\":\"\",\"data\":null}\n```\n\nThe same value read back anonymously:\n\n```\nPOST http://127.0.0.1:6808/api/storage/getOutlineStorage\n{\"docID\":\"<doc id>\"}\n→ {\"code\":0,\"msg\":\"\",\"data\":{\"openIDs\":[\"<heading id>\",\"<heading id>\"]}}\n```\n\nWith that document set to the forbidden tier, on the same anonymous session:\n\n| Endpoint | Result |\n|---|---|\n| `getDoc` (control) | `protyle-password--forbidden` placeholder, content withheld |\n| `getOutlineStorage` | full payload returned |\n\nThe control establishes that the session is correctly denied the document itself.\n\n### Impact\n\nAn anonymous reader in publish mode, or any publish `RoleReader`, retrieves the administrator's outline state for any document whose identifier they hold, including documents in the forbidden tier that the publish filters otherwise withhold entirely. The disclosed values are heading block identifiers, usable as input to other endpoints, and the presence or absence of an entry indicates whether the administrator has worked with that document.\n\nNo document text is returned. Confidentiality only.\n\n### Suggested fix\n\nGate the read path as the write paths already are. Either add `CheckAdminRole` and `CheckReadonly` at the route, matching `setOutlineStorage` and `removeOutlineStorage`, or pass `*gin.Context` into `GetOutlineStorage` and apply `checkBlockTreeAccessableByPublishAccess` against the requested `docID` before returning anything.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/siyuan-note/siyuan/kernel"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.0.0-20260812083335-251596fc0de2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/siyuan-note/siyuan/security/advisories/GHSA-53fp-9jmv-227g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-73607"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/siyuan-note/siyuan"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/siyuan-note/siyuan/releases/tag/v3.8.0"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/siyuan-before-information-disclosure-via-getoutlinestorage"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-01T15:44:46Z",
    "nvd_published_at" : null
  }
}