SiYuan: Anonymous publish-password authentication bypass via getHeadingChildrenDOM / getHeading*Transaction / getBacklinkDoc (publish mode)

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-68584: 0.53% estimated exploitation activity in the next 30 days; percentile 45.17 (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-68584. Summary SiYuan's publish mode defines a "protected" access level: a document that is publicly listed but requires a password to read (per the product's own UI help text, protected = "Publicly visible, requires password to access"). The password is enforced on the primary content path (getDoc, via FilterContentByPublishAccess). Several other content-returning endpoints getHeadingChildrenDOM, getHeadingDeleteTransaction/getHeadingLevelTransaction/ getHeadingInsertTransaction, and getBacklinkDoc/getBackmentionDoc return rendered block DOM with no password check at all. Combined with reader-reachable endpoints that leak a protected document's internal block IDs, an anonymous reader can retrieve the full body of a password-protected document without the password. This has been reproduced end-to-end on a live instance. Details The password control and where it is enforced. Publish access has five levels encoded in…

Published by the source

3 Sep 2026, 21:22 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-7j72-f6wg-cxw6

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6382

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7j72-f6wg-cxw6

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

# Patch Next advisory brief: CVE-2026-68584

Advisory: SiYuan: Anonymous publish-password authentication bypass via getHeadingChildrenDOM / getHeading*Transaction / getBacklinkDoc (publish mode)
IDs: CVE-2026-68584, GHSA-7j72-f6wg-cxw6
Record: https://patchnext.com/advisories/cve-2026-68584 (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-20260721020826-2d069dce84a2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/siyuan-note/siyuan/kernel: affected < 0.0.0-20260721020826-2d069dce84a2; fixed in 0.0.0-20260721020826-2d069dce84a2

## 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-7j72-f6wg-cxw6 (OSV record GHSA-7j72-f6wg-cxw6 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721020826-2d069dce84a2 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6382 (OSV record GO-2026-6382 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721020826-2d069dce84a2 (fixed))
- Verified: https://github.com/advisories/GHSA-7j72-f6wg-cxw6 (GitHub-reviewed advisory GHSA-7j72-f6wg-cxw6 lists affected ranges: Go github.com/siyuan-note/siyuan/kernel >=0 <0.0.0-20260721020826-2d069dce84a2)

Commands are suggestions: review each one before running it.