CVE-2026-72789: SiYuan Information Disclosure Vulnerability

CVE-2026-72789 Overview

CVE-2026-72789 is a missing authorization vulnerability [CWE-862] in SiYuan, a self-hosted personal knowledge management application. Versions before v3.7.4 fail to validate publish access for encrypted notebooks, treating them as publicly accessible by default. Anonymous readers can enumerate and retrieve fully decrypted document content from unlocked encrypted notebooks through the publish API. The attack requires no authentication, no user interaction, and no key material. Attackers can access the plaintext contents of notebooks that users explicitly encrypted for confidentiality.

Critical Impact
Unauthenticated network attackers can read decrypted contents of encrypted SiYuan notebooks through the publish API, defeating the encryption protection users applied to sensitive documents.

Affected Products

SiYuan note-taking application
All versions prior to v3.7.4
Deployments exposing the SiYuan publish API to untrusted networks

Discovery Timeline

2026-08-12 - CVE-2026-72789 published to NVD
2026-08-12 - Last updated in NVD database

Technical Details for CVE-2026-72789

Vulnerability Analysis

The vulnerability resides in SiYuan's publish API authorization logic. The application exposes a publish endpoint intended to share selected content, but it does not enforce access controls on encrypted notebooks. When an encrypted notebook is unlocked in the running SiYuan instance, its decrypted contents become reachable through the publish API without any authentication challenge.

Encrypted notebooks are designed to protect sensitive documents with key material supplied by the user. The publish handler bypasses this protection by treating encrypted notebooks as publicly published resources. Anonymous callers can enumerate notebooks, list documents, and download plaintext content directly. See the GitHub Security Advisory and the VulnCheck Advisory on Siyuan for the vendor and third-party analysis.

Root Cause

The root cause is missing authorization [CWE-862] in the publish API path. The application does not check whether the requesting principal is authorized to access an encrypted notebook before serving its decrypted content. Encryption state is not evaluated as a gating condition for publish access.

Attack Vector

The attack vector is network-based and requires no privileges or user interaction. An attacker who can reach the SiYuan HTTP interface issues requests to the publish API and enumerates encrypted notebooks that have been unlocked. The server returns decrypted document contents in the response. Exposure is highest for SiYuan instances published to the internet or accessible on shared corporate networks.

No verified proof-of-concept code has been published. Refer to the linked advisories for reproduction details.

Detection Methods for CVE-2026-72789

Indicators of Compromise

Unauthenticated HTTP requests to SiYuan publish API endpoints from unexpected source addresses
Bulk enumeration patterns against the publish API followed by document retrieval requests
Access log entries returning 200 responses for encrypted notebook resources without a corresponding authenticated session

Detection Strategies

Inventory SiYuan deployments and identify instances running versions before v3.7.4
Review reverse proxy and web server access logs for anonymous requests to publish API routes targeting notebook identifiers
Alert on external network sources reaching SiYuan services that were intended for local or authenticated use only

Monitoring Recommendations

Monitor egress traffic from SiYuan hosts for unusual data volumes indicating notebook exfiltration
Track authentication state on publish API requests and flag responses served without a valid session
Correlate publish API access with the list of notebooks marked as encrypted to detect unauthorized reads

How to Mitigate CVE-2026-72789

Immediate Actions Required

Upgrade SiYuan to v3.7.4 or later on all hosts running the application
Restrict network exposure of SiYuan instances to trusted networks or place them behind an authenticating reverse proxy
Lock encrypted notebooks when not actively in use to reduce the window in which decrypted content is reachable

Patch Information

The issue is fixed in SiYuan v3.7.4. The vendor advisory is published at the GitHub Security Advisory GHSA-v684-q882-jgmq. Administrators should apply the update as the primary remediation, then rotate any secrets that may have been stored in exposed notebooks.

Workarounds

Block inbound access to the SiYuan publish API at the network or reverse proxy layer until the patch is applied
Require an external authentication layer, such as a reverse proxy enforcing HTTP Basic or SSO, in front of SiYuan
Keep encrypted notebooks locked and avoid unlocking them on instances that are reachable from untrusted networks

bash

# Example nginx configuration restricting the SiYuan publish API to trusted addresses
location /api/publish/ {
    allow 10.0.0.0/8;
    allow 192.168.0.0/16;
    deny all;
    proxy_pass http://127.0.0.1:6806;
}