SiYuan: Full-content disclosure of publish-disabled documents via getHeading*Transaction endpoints (publish mode): reader-reachable rendered DOM with no publish-access check

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-68587: 0.32% estimated exploitation activity in the next 30 days; percentile 25.18 (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-68587. Summary Three "heading transaction" endpoints /api/block/getHeadingDeleteTransaction, /api/block/getHeadingLevelTransaction, and /api/block/getHeadingInsertTransaction return the rendered block DOM of a heading and its subtree in the computed transaction payload, with no publish-access check. They are gated by CheckAuth only, so they are reachable by the publish RoleReader token, and by the anonymous account when Publish.Auth.Enable is false. Despite their write-implying names, these endpoints perform no mutation on this path, they compute a transaction object and return it, and that object contains RenderNodeBlockDOM output. As a result, an anonymous reader who supplies a heading block ID can read the full rendered content of a document that has been explicitly marked publish-disabled by an administrator, content that the reader-facing /api/filetree/getDoc path correctly refuses to return. Details Route / auth tier. All three…

Published by the source

3 Sep 2026, 21:19 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-69mh-gvh4-8gp7

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6381

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-69mh-gvh4-8gp7

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

# Patch Next advisory brief: CVE-2026-68587

Advisory: SiYuan: Full-content disclosure of publish-disabled documents via getHeading*Transaction endpoints (publish mode): reader-reachable rendered DOM with no publish-access check
IDs: CVE-2026-68587, GHSA-69mh-gvh4-8gp7
Record: https://patchnext.com/advisories/cve-2026-68587 (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-20260721013353-69db783b782a. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260721013353-69db783b782a; fixed in 0.0.0-20260721013353-69db783b782a

## 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-69mh-gvh4-8gp7 (OSV record GHSA-69mh-gvh4-8gp7 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721013353-69db783b782a (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6381 (OSV record GO-2026-6381 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721013353-69db783b782a (fixed))
- Verified: https://github.com/advisories/GHSA-69mh-gvh4-8gp7 (GitHub-reviewed advisory GHSA-69mh-gvh4-8gp7 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721013353-69db783b782a)

Commands are suggestions: review each one before running it.