Document existence disclosure via response discrepancies
Published Aug 14, 2026 · Updated Aug 14, 2026
Information disclosure in SiYuan before 3.7.4 allows remote attackers to confirm hidden or forbidden documents via publish requests. The /api/filetree/authFilePublishAccess handler leaves failures at code 0 and varies its message and Set-Cookie behavior by access tier; an empty password also matches hidden and forbidden entries. Publish mode must be enabled, and an attacker needs a candidate document identifier; the oracle reveals existence and tier but no content or privilege.
Summary
What happened
Information disclosure in SiYuan before 3.7.4 allows remote attackers to confirm hidden or forbidden documents via publish requests. The /api/filetree/authFilePublishAccess handler leaves failures at code 0 and varies its message and Set-Cookie behavior by access tier; an empty password also matches hidden and forbidden entries. Publish mode must be enabled, and an attacker needs a candidate document identifier; the oracle reveals existence and tier but no content or privilege.
The record
- CVE
- CVE-2026-73630
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- SiYuan Note
- Product
- SiYuan
- Classifications
- CWE-203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.7.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream authFilePublishAccess proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo