CVE-2026-72810: SiYuan publish-boundary bypass via WebSocket broadcast

CVE-2026-72810 · Severity: high · CVSS 8.6 · Published 2026-09-03

SiYuan is a note-taking and knowledge management application that supports a publish mode for sharing content. This vulnerability allows anonymous readers or any user with read access in publish mode to passively receive a live, real-time stream of all document edits—including those marked as password-protected, unpublished, or forbidden—by simply keeping a WebSocket connection open. The attacker gains access to sensitive metadata and content without any active interaction, defeating all publish-access and password protections for edits made while connected.

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

Quick answers

Is CVE-2026-72810 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-72810 being exploited in the wild.
How severe is CVE-2026-72810?
High severity, with a CVSS score of 8.6, published 3 September 2026.
Which products and versions are affected?
github.com/siyuan-note/siyuan/kernel (Go) < 0.0.0-20260723013612-ba948639d7f6, SEMVER:introduced=0,fixed=0.0.0-20260723013612-ba948639d7f6; SiYuan < 0.0.0-20260723013612-ba948639d7f6.
Is there a fix for CVE-2026-72810?
Yes. github.com/siyuan-note/siyuan/kernel (Go): upgrade to 0.0.0-20260723013612-ba948639d7f6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-72810 attacked?
It is attacked over the network.
Am I affected by CVE-2026-72810?
Check whether you run github.com/siyuan-note/siyuan/kernel (Go) or SiYuan 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-20260723013612-ba948639d7f6 or later
    go get github.com/siyuan-note/siyuan/kernel@v0.0.0-20260723013612-ba948639d7f6

Technical details

The vulnerability is a missing authorization check (CWE-862) in SiYuan's WebSocket broadcast mechanism used for real-time synchronization. When publish mode is enabled with authentication disabled, the `HandleConnect` function admits anonymous `RoleReader` tokens and registers them in the same broadcast session pool as authenticated clients. The kernel's broadcast functions (`Broadcast`, `broadcastOthers`, etc.) transmit content events—including document transactions with DOM rendering, create/save events, move/rename operations—to all sessions in the pool without applying any publish-access, publish-password, or role-based filtering. The `isPublish` flag exists on sessions but is only used to send a service-closed notice, not to gate content. Because events are pushed directly over WebSocket from the kernel's edit pipeline, they bypass all HTTP-layer publish-access filters. A network-reachable attacker with no privileges can open a WebSocket connection to the publish surface (port 6808) and passively receive unfiltered edits, including metadata and content from password-protected or unpublished documents, as long as they hold the connection open while edits occur. Patch 0.0.0-20260723013612-ba948639d7f6 is available.

Affected products

  • siyuan-note siyuan < 0.0.0-20260723013612-ba948639d7f6

Identifiers

  • CVE-2026-72810
  • GHSA-mw8r-mw84-88v2
  • GO-2026-6400

Timeline

  • 2026-09-03: disclosed: GitHub Security Advisory published
  • 2026-07-23: patched: Patch commit ba948639d7f6 available

References

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