SiYuan CVE-2026-68584

Exploitation requires that the target SiYuan instance is running in publish mode and network-reachable, and that the confidentiality being attacked comes from publish-mode password-protected documents - that specific feature combination is the prerequisite named in the advisory. Given AV:N/AC:L/PR:N/UI:N, no authentication, credentials, or user interaction are needed once publish mode is exposed. The primary limiting factor is deployment: instances that do not enable publish mode, or that keep it behind separate network/reverse-proxy authentication, are not exposed; the attacker also needs valid internal block IDs, but these are obtainable from other reader-accessible endpoints, so it is not a meaningful barrier.

This is a genuine high-priority confidentiality issue for anyone running SiYuan in publish mode with password-protected documents. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/SC:H) scoring 9.2 aligns well with the description: no authentication, no user interaction, low complexity, network-reachable, and high confidentiality impact including a subsequent-system impact (the protected content behind the gate). Unlike many high-CVSS scores that overstate real risk, the signals here are internally consistent - the only real precondition is that publish mode is actually enabled and exposed, which is a deliberate, non-default deployment choice that limits the exposed population. No EPSS score, no POC, and no KEV listing were provided, so exploitation is currently assessed as opportunistic-potential rather than confirmed active; the low product footprint further reduces mass-exploitation likelihood. Integrity and availability are unaffected (VI:N/VA:N) - this is read-only disclosure, not takeover.

An organization publishes an internal SiYuan notebook in publish mode and locks a few sensitive documents behind passwords. An unauthenticated attacker on the network enumerates reader-accessible endpoints to collect internal block IDs, then calls getHeadingChildrenDOM/getBacklinkDoc with those IDs and receives the protected document content without ever supplying the password. Given AV:N/AC:L/PR:N/UI:N, this requires only network reach to the publish endpoint and simple scripted requests; no public POC has been identified at time of analysis.