Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-7j72-f6wg-cxw6

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

CVSS 9.2 CriticalCriticalEPSS 0.0053 · 45th percentile

Critical, because:

  • CVSS score 9.2: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Sept 2026, 21:22 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/siyuan-note/siyuan/kernelGo<0.0.0-20260721020826-2d069dce84a20.0.0-20260721020826-2d069dce84a2
Identifiers
GHSA-7j72-f6wg-cxw6 · CVE-2026-68584 · GO-2026-6382
Weakness (CWE)
CWE-288
Tags
Published
3 Sept 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected: SiYuan's Go kernel (github.com/siyuan-note/siyuan/kernel) before 0.0.0-20260721020826-2d069dce84a2, which is also the fixed version. In publish mode, several endpoints that return rendered block content (getHeadingChildrenDOM, the getHeading*Transaction handlers, getBacklinkDoc and getBackmentionDoc) skip the password check that protects password-protected documents. An anonymous reader, or any publish reader, can obtain block IDs from other endpoints and then read the full body of a protected document without its password. Upgrade to 0.0.0-20260721020826-2d069dce84a2 or later.

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

ScoreRatingCVSSVectorSource
9.2 Critical 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0053, the 45th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

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.