SiYuan: Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlineStorage with no access check

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-73607: 0.25% estimated exploitation activity in the next 30 days; percentile 16.74 (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.

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: 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…

Published by the source

1 Oct 2026, 15:44 UTC

Last modified by the source

7 Oct 2026, 17:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-53fp-9jmv-227g

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6624

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-53fp-9jmv-227g

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

# Patch Next advisory brief: CVE-2026-73607

Advisory: SiYuan: Outline state for any document, including documents forbidden to readers, is returned by /api/storage/getOutlineStorage with no access check
IDs: CVE-2026-73607, GHSA-53fp-9jmv-227g
Record: https://patchnext.com/advisories/cve-2026-73607 (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-20260812083335-251596fc0de2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260812083335-251596fc0de2; fixed in 0.0.0-20260812083335-251596fc0de2

## 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/GO-2026-6624 (OSV record GO-2026-6624 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-53fp-9jmv-227g (OSV record GHSA-53fp-9jmv-227g lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2 (fixed))
- Verified: https://github.com/advisories/GHSA-53fp-9jmv-227g (GitHub-reviewed advisory GHSA-53fp-9jmv-227g lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260812083335-251596fc0de2)

Commands are suggestions: review each one before running it.