CVE-2026-72804: SiYuan: Graph endpoints omit the publish-password tier: anonymous readers receive block-level content of password-protected documents
CVE: This vulnerability corresponds to CVE-2026-72804. Summary getGraph and getLocalGraph filter reader sessions against the visibility tier only and never check the publish password. Password-protected documents are Visible = true, so their graph nodes survive the filter and graph nodes are block-level and carry the block's actual content.
Published Sep 3, 2026
Affected packages
github.com/siyuan-note/siyuan/kernel
- Ecosystem
- Go
- Affected
- < 0.0.0-20260724091654-82e9ded423e4
- Fixed in
- 0.0.0-20260724091654-82e9ded423e4
- Check
go list -m github.com/siyuan-note/siyuan/kernel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
CVE: This vulnerability corresponds to CVE-2026-72804.
Summary
getGraph and getLocalGraph filter reader sessions against the *visibility* tier only and never check the publish password. Password-protected documents are Visible = true, so their graph nodes survive the filter and graph nodes are block-level and carry the block's actual content. An anonymous reader who has never supplied a document's password can therefore retrieve that document's per-block content and its reference/backlink topology. Both endpoints are CheckAuth-only, so they are reachable by the publish RoleReader token and by the anonymous account when Publish.Auth.Enable is false.
Details
Both handlers filter with the invisible-tier set only:
publishIgnore := model.GetInvisiblePublishAccess(publishAccess) // Visible tier ONLY
nodes, links = model.FilterGraphByPublishIgnore(publishIgnore, nodes, links)FilterGraphByPublishIgnore (kernel/model/publish_access.go:849) drops a node only when !CheckPathAccessableByPublishIgnore(node.Box, node.Path, publishIgnore). There is no password evaluation anywhere in the graph code grepping graph.go for CheckPublishAuthCookie or password returns nothing.
Because password-protected documents are Visible = true, their nodes pass the filter unchanged.
The nodes carry content, not just titles. genTreeNodes emits one node per block, and nodeTitleLabel sets node.Title = node.Label = block.Content (kernel/model/graph.go:673-678). So each surviving node exposes the block's text.
This is materially broader than the by-design listing behaviour: listDocsByPath intentionally exposes protected document *titles* (protected means "publicly visible, password required to access"), but the graph endpoints expose per-block *content* and the full link/reference topology, which listing never does.
Verified at origin/master: FilterGraphByPublishIgnore contains only the CheckPathAccessableByPublishIgnore call; graph.go contains no password check; both routes are registered CheckAuth without CheckAdminRole.
Proof of Concept
Precondition: publish mode enabled (default port 6808); anonymous when Publish.Auth.Enable is false, otherwise any publish reader account. A document is marked protected (visible, password set) and contains blocks with distinctive content. No password is supplied in any request below.
Targeted: one protected document's content and reference structure:
POST http://127.0.0.1:6808/api/graph/getLocalGraph
{"id":"<PROTECTED_DOC_ID>"}Returns nodes whose Title/Label contain the protected document's per-block content, plus its links/backlinks.
Workspace-wide: every protected document:
POST http://127.0.0.1:6808/api/graph/getGraph
{}Returns block-level nodes for every protected document in the workspace, together with the complete link graph.
Control: requesting the same document through the normal content path returns the password placeholder confirming the password gate is enforced elsewhere and omitted here.
Impact
An anonymous reader (publish mode with auth disabled) or any publish RoleReader can read the block-level content of every password-protected document in the workspace, plus the full reference/backlink topology, without ever supplying a password. This defeats the publish-password control for the graph subsystem. Confidentiality-only, no modification.
Suggested fix
Extend the graph filter to evaluate the password tier in addition to visibility: in FilterGraphByPublishIgnore, drop a node unless the document's publish password is unset or the caller presents a valid publish-auth cookie for it (password == "" || CheckPublishAuthCookie(...)), matching the sibling filters that enforce both tiers. Consider also excluding block content from node Title/Label for reader sessions, so the graph conveys structure without document text.
Credited to Shirshakhtml.
References
- https://github.com/siyuan-note/siyuan/security/advisories/GHSA-vpjw-wf5h-cgpq
- https://nvd.nist.gov/vuln/detail/CVE-2026-72804
- https://github.com/siyuan-note/siyuan/commit/82e9ded423e45eabcc96010abd30c0f96bfe0323
- https://www.vulncheck.com/advisories/siyuan-before-authentication-bypass-via-graph-endpoints
- https://github.com/advisories/GHSA-vpjw-wf5h-cgpq
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-60083
SiYuan: MCP file tool's blocklist is incomplete relative to the HTTP file API it claims to align with, exposing publish-mode passwords and other sensitive workspace files
medium4.9Oct 27, 2026CVE-2026-62204
SiYuan: Missing consistency check between packageName and repoURL/repoHash in bazaar package install allows overwriting an existing, trusted plugin
medium6.6Oct 23, 2026CVE-2026-73049
SiYuan: The publish filter for database backlinks consults the forbidden list instead of the visibility list, disclosing hidden-tier documents to anonymous readers
medium5.8Oct 23, 2026CVE-2026-73054
SiYuan: A parser differential between the WebSocket keepalive exemption and the session quarantine allows unauthenticated access to the broadcast event stream
high7.5Oct 23, 2026CVE-2026-73630
SiYuan: authFilePublishAccess distinguishes hidden and forbidden documents from public and nonexistent ones, and issues a publish-auth cookie for documents it reports as forbidden
medium5.8Oct 23, 2026GHSA-xp3q-r38w-vgqm
SiYuan: The publish filter for local storage returns the administrator's entire storage map with only three keys sanitized
medium5.8Oct 23, 2026
