Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-69mh-gvh4-8gp7

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

CVSS 9.2 CriticalCriticalEPSS 0.0032 · 25th 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:19 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-20260721013353-69db783b782a0.0.0-20260721013353-69db783b782a
Identifiers
GHSA-69mh-gvh4-8gp7 · CVE-2026-68587 · GO-2026-6381
Weakness (CWE)
CWE-862
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.

GHSA-69mh-gvh4-8gp7: The Go module github.com/siyuan-note/siyuan/kernel is affected at versions before 0.0.0-20260721013353-69db783b782a, which is also the fixed version. Three heading transaction endpoints (getHeadingDeleteTransaction, getHeadingLevelTransaction, getHeadingInsertTransaction) return rendered DOM of a heading and its subtree without the publish-access check, so an anonymous reader or publish reader who knows a heading block ID can read content of a document marked publish-disabled. Upgrade to 0.0.0-20260721013353-69db783b782a 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.0032, the 25th 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.