CVE-2026-72804: SiYuan graph endpoints bypass publish password protection

CVE-2026-72804 · Severity: high · CVSS 8.6 · Published 2026-08-12

SiYuan is a popular note-taking and knowledge management application that allows users to publish documents with optional password protection. An attacker can bypass these password protections by calling the graph API endpoints (`getGraph` and `getLocalGraph`) without providing a password, gaining access to the full text content and internal linking structure of all password-protected documents in the workspace. This is a serious confidentiality breach that affects anyone using SiYuan's publish feature with authentication disabled or as a reader.

Technologies: github.com/siyuan-note/siyuan/kernel (Go). Vendors: Go.

Quick answers

Is CVE-2026-72804 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-72804 being exploited in the wild.
How severe is CVE-2026-72804?
High severity, with a CVSS score of 8.6, published 12 August 2026.
Which products and versions are affected?
github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260724091654-82e9ded423e4, SEMVER:introduced=0,fixed=0.0.0-20260724091654-82e9ded423e4.
Is there a fix for CVE-2026-72804?
Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260724091654-82e9ded423e4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-72804 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-72804?
Check whether you run github.com/siyuan-note/siyuan/kernel (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260724091654-82e9ded423e4 or later
    go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260724091654-82e9ded423e4

Technical details

The vulnerability stems from missing authorization checks in the graph endpoint handlers. Both `getGraph` and `getLocalGraph` filter graph nodes using `FilterGraphByPublishIgnore()`, which only evaluates the visibility tier (checks the invisible-tier set) but contains no password evaluation logic. Password-protected documents are marked `Visible = true` and therefore pass the filter unchanged. Furthermore, graph nodes carry block-level content (not just titles), as `genTreeNodes()` sets `node.Title = node.Label = block.Content`. The endpoints are registered with `CheckAuth` only, making them reachable by any publish reader token or anonymous users when `Publish.Auth.Enable` is disabled. The attack requires no user interaction and no authentication beyond what is already granted to readers.

Affected products

  • siyuan-note siyuan before 0.0.0-20260724091654-82e9ded423e4

Identifiers

  • CVE-2026-72804
  • GHSA-vpjw-wf5h-cgpq
  • GO-2026-6407

Timeline

  • 2026-07-24: disclosed: Published to GitHub Advisory Database
  • 2026-09-03: advisory: GHSA-vpjw-wf5h-cgpq published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.